Your Docker Compose file uses relative paths (e.g., ./config/...), which can be problematic when deploying through Portainer because the context directory might not be what you expect. Portainer might not have access to the same filesystem structure as your local development environment. Here are some steps and adjustments you can make to ensure it works properly:
General Adjustments
Use Absolute Paths: When deploying with Portainer, it's better to use absolute paths for volumes to ensure the paths are correctly resolved.
Verify Paths: Ensure all paths referenced in your docker-compose.yml actually exist on your host machine and are accessible.
Permissions: Ensure the user running Portainer has the necessary permissions to access the files and directories specified.
One step to the right direction would be is to specify these /absolute/path/to/
Hello, good day!
Your Docker Compose file uses relative paths (e.g.,
./config/...
), which can be problematic when deploying throughPortainer
because the context directory might not be what you expect.Portainer
might not have access to the same filesystem structure as your local development environment. Here are some steps and adjustments you can make to ensure it works properly:General Adjustments
Use Absolute Paths: When deploying with
Portainer
, it's better to use absolute paths for volumes to ensure the paths are correctly resolved.Verify Paths: Ensure all paths referenced in your
docker-compose.yml
actually exist on your host machine and are accessible.Permissions: Ensure the user running
Portainer
has the necessary permissions to access the files and directories specified.One step to the right direction would be is to specify these
/absolute/path/to/
Applying these changes should help resolve #29
If any of the config files are containing some path on your machine please also make it clear if it required to be specified.
example:
logs
folder in the git root folder. I assume this one needs an absolute path as well. netprobe, logging_helper, presentation