-
Notifications
You must be signed in to change notification settings - Fork 8.1k
engine: storage/mounts freshness #21420
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
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
f12ad59 to
f43d4de
Compare
thaJeztah
left a comment
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.
just some first comments; will need to take a closer look later
28e9388 to
710cae8
Compare
7eeb4a0 to
0ace39d
Compare
| > Working with large repositories or monorepos, or with virtual file systems that are no longer scaling with your codebase? | ||
| > Check out [Synchronized file shares](/manuals/desktop/features/synchronized-file-sharing.md). It provides fast and flexible host-to-VM file sharing by enhancing bind mount performance through the use of synchronized filesystem caches. |
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.
Do we still need to refer to the features provided by Docker Desktop? For example, currently we do mention that bind-mounts are created on the daemon host, but it may be relevant to the user that with Docker Desktop we provide extra mechanisms to make that work for host locations (but at a performance penalty for having to bridge / synchronise to the daemon host (VM))
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.
OK, I added this:
diff --git a/content/manuals/engine/storage/bind-mounts.md b/content/manuals/engine/storage/bind-mounts.md
index e00820e90e..4b5d07c09d 100644
--- a/content/manuals/engine/storage/bind-mounts.md
+++ b/content/manuals/engine/storage/bind-mounts.md
@@ -60,6 +60,11 @@ the mount.
If you're using a remote Docker daemon, you can't create a bind mount to
access files on the client machine in a container.
+ For Docker Desktop, the daemon runs inside a Linux VM, not directly on the
+ native host. Docker Desktop has built-in mechanisms that transparently handle
+ bind mounts, allowing you to share native host filesystem paths with
+ containers running in the virtual machine.
+
- Containers with bind mounts are strongly tied to the host.
Bind mounts rely on the host machine's filesystem having a specific directoryThere 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.
Thanks! Yup, that works for me 👍
| - Bind mounts are created to the Docker daemon host, not the client. | ||
|
|
||
| If you're using a remote Docker daemon, you can't create a bind mount to | ||
| access files on the client machine in a container. |
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 probably should've put that previous comment somewhere here)
Signed-off-by: David Karlsson <[email protected]>
0ace39d to
4838945
Compare
Signed-off-by: David Karlsson <[email protected]>
4838945 to
ba7c7c6
Compare
thaJeztah
left a comment
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.
LGTM
Various freshness updates to improve the flow and structure of the documentation related to storage mounts.
Preview: