-
Notifications
You must be signed in to change notification settings - Fork 118
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
Mounting subdirectories of symlinks into containers is not possible #412
Comments
Thanks for reporting this. This is an issue with the OS X directory chooser that does not allow the user to select paths with unresolved components (only the last component remains unresolved if the option to retain verbatim paths is used). We need to use a different method to select the paths to export to Docker. This issue has been tracked internally since August 16 and I have started a thread with our GUI team about getting it resolved. Thanks for using Docker for Mac and sorry for this annoying problem. |
Thank you for your reply. |
+1 to this issue |
If this can help, you can use NFS mounts instead of D4M shares, this should let you more flexibility (and speed ^^). |
Just some update, I managed to mount directories via symlinks using |
This was fixed in Beta 33 and has been recently improved in Beta 35 or 36 so that exported directory paths are editable and now manually enterable by editing a blank entry at the end of the list. Thanks for your patience with this issue and for using Docker for Mac. This improvement should reach the stable channel in a week or two. |
After I upgrade to the latest version on Mac os 10.15.3. I get I try to mount If I try to run
I also post a question here |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
In my setup, I mount a subfolder of etc into my docker container (e.g. /etc/foo). (On OS X '/etc' is actually a symlink to "/private/etc".) I want to be able to use the same scripts on Linux and on OS X machines, so I use the /etc/foo path for mounting these folders.
The /etc folder is not shared as default with docker, so I tried adding "/etc" to the shared folders but I got a message saying, that "/etc is reserved by docker". When I try to add "/etc/foo" directly to the shared folders, it gets resolved to "/private/etc/foo".
Currently I see no possibility to mount "/etc/foo" on OS X into a docker container though it works on Linux systems.
Is there a reason for this restriction, or is it just an oversight, as adding "/etc/foo" to the shared folders should work but is broken by the system's folder selection which resolves the symlink?
Thank you for your help.
The text was updated successfully, but these errors were encountered: