-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use mount instead of volume in docker compose file to avoid creating empty directories for missing files #473
Comments
As I have realized this is going to require some changes to I think the part we really want in the documentation is here: Volumes: Long Syntax My rough-and-dirty attempt at find-and-replace in my text editor is (still requires some manual tweaking): Find: in |
…n the docker-compose.yml yet, this commit makes LocalPathForContainerBindMount work for when I do. it's backwards compatible with the old short-style mount options as well
Testing now. Rather than create the empty directory (which is root-owned and often causes all sorts of headaches to clean up), now you get something like this:
All of the necessary files/directories SHOULD be created by install and auth_setup, but if for some reason they're not now we'll know it. |
See Differences between -v and --mount behavior:
Generating an error would be way preferable to creating an empty directory for our bind mounts.
As far as how to do this:
The text was updated successfully, but these errors were encountered: