Skip to content

Conversation

@dvdksn
Copy link
Contributor

@dvdksn dvdksn commented Nov 13, 2024

Various freshness updates to improve the flow and structure of the documentation related to storage mounts.

  • Make the storage overview page shorter, deduplicating some content and moving other, mount-specific content over into the corresponding page
  • Improve the documentation for the various mount options, and make sure all the available mount options are documented
  • Fix various style/wording nits

Preview:

@netlify
Copy link

netlify bot commented Nov 13, 2024

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit ba7c7c6
🔍 Latest deploy log https://app.netlify.com/sites/docsdocker/deploys/6752fe9af66b9600084f8090
😎 Deploy Preview https://deploy-preview-21420--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@github-actions github-actions bot added area/engine Issue affects Docker engine/daemon area/storage Relates to storage, volumes area/tests labels Nov 13, 2024
@dvdksn dvdksn force-pushed the engine-storage-freshness branch from f12ad59 to f43d4de Compare November 13, 2024 14:48
@dvdksn dvdksn requested review from a team, thaJeztah and vvoland November 13, 2024 14:51
@dvdksn dvdksn marked this pull request as ready for review November 13, 2024 14:51
Copy link
Member

@thaJeztah thaJeztah left a 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

@dvdksn dvdksn force-pushed the engine-storage-freshness branch 2 times, most recently from 28e9388 to 710cae8 Compare November 18, 2024 09:31
@dvdksn dvdksn force-pushed the engine-storage-freshness branch 2 times, most recently from 7eeb4a0 to 0ace39d Compare November 29, 2024 08:25
aevesdocker
aevesdocker previously approved these changes Nov 29, 2024
@dvdksn dvdksn requested review from thaJeztah and vvoland December 5, 2024 16:19
Comment on lines -30 to -31
> 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.
Copy link
Member

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))

Copy link
Contributor Author

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 directory

Copy link
Member

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 👍

Comment on lines +58 to +61
- 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.
Copy link
Member

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)

@dvdksn dvdksn force-pushed the engine-storage-freshness branch from 4838945 to ba7c7c6 Compare December 6, 2024 13:39
Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thaJeztah thaJeztah merged commit c176c2d into docker:main Dec 9, 2024
14 checks passed
@dvdksn dvdksn deleted the engine-storage-freshness branch December 9, 2024 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/engine Issue affects Docker engine/daemon area/storage Relates to storage, volumes area/tests status/review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants