I think this has to do with the way Docker handles bind mounts. When you point to a file, the Docker assigns an inode when the container is created. This inode is not updated if the file is changed outside Docker.

The proper solution would be to use a directory bind mount, instead of a file bind mount. From what I can see, there are other files stored in /app/public, so that wouldn't work with the current code base. I would suggest moving the conf.yml to it's own isolated folder and updating the volume mapping in the docker-compose to point to that folder rather than explicitly to the file.

There's a pretty good example of what I'm trying to say here: https://medium.com/@jonsbun/why-need-to-be-careful-when-mounting-single-files-into-a-docker-container-4f929340834

Why need to be careful when mounting single files into a Docker container

If you ever had a situation when mounted file inside Docker container and on the host is different (not in sync)? If yes, this is mean…

[QUESTION] Config not working on docker? #142

Company

Community

Support

Connect