-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
Add a note to point out to new users that B2D bind-mounts are special-ish #9491
Add a note to point out to new users that B2D bind-mounts are special-ish #9491
Conversation
> (OSX) / `C:/Users` (Windows) directory - and so will only allow you to host mount | ||
> using `docker run -v /Users/path:/ContainerDir ...` (OSX) or | ||
> `docker run -v /c/Users/path:/ContainerDir ...` (Windows). All other paths would | ||
> be internal to the Boot2Docker virtual machine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
paths are internal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i can't think of another way to note that if you do -v /etc:/banana
, from OSX, then the /etc
comes from the inner vm's fs, not from the outer OSX host fs. - suggestions?
LGTM minor comments. |
But FUSE is soooo buggy On Wed, Dec 3, 2014 at 6:10 PM, Justin Mayer notifications@github.com
|
@jfrazelle, actually it's programs using the FUSE interface more often than not that are buggy and slow (often due to being written in C with no concurrency story), not the FUSE code in Linux itself. OS X FUSE has a less great track record, but that isn't even relevant here, because this FUSE only runs inside Linux in the Boot2Docker VM. The host machine (Windows, Mac, etc) never runs any FUSE part. |
Ah ok cool, my experience with FUSE has been purely OS X based in the past, looking over the branch you linked, seems pretty straight forward, I do agree this shouldn't close the issue |
if my marking this pr as closing the other prompts some more work on fuse and remote volumes, then YAY :) |
69fe1ce
to
0d7c604
Compare
|
||
> **Note:** | ||
> If you are using Boot2Docker, your Docker daemon only has limited access to | ||
> your OSX/Windows host directory. Boot2Docker tries to auto share your `/Users` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
auto-share
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
delete "only"
@SvenDowideit A couple of nits and a bit that needs some revision. |
…-ish Docker-DCO-1.1-Signed-off-by: Sven Dowideit <SvenDowideit@docker.com> (github: SvenDowideit) Signed-off-by: Sven Dowideit <SvenDowideit@docker.com>
0d7c604
to
e529885
Compare
@fredlf is that better? |
Yes, much better. I still think there's part of a thought missing between the first and second sentence, but it's good enough to publish. Thanks @SvenDowideit |
…re-special Add a note to point out to new users that B2D bind-mounts are special-ish
…2d-are-special Add a note to point out to new users that B2D bind-mounts are special-ish (cherry picked from commit 880aeab) Docker-DCO-1.1-Signed-off-by: Fred Lifton <fred.lifton@docker.com> (github: SvenDowideit)
to help with some user confusion mentioned in #4023
@fredlf @jamtur01