From ae96cdfca0d079bc0fbcec91b304933a1168265c Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Tue, 21 Jul 2026 10:27:57 +0000 Subject: [PATCH] docs: correct read-only volume wording (fixes #11159) The read-only volume section incorrectly described the mount as a bind mount. Refer to the mounted data as a volume and remove the host propagation claim. Co-Authored-By: Codex --- content/manuals/engine/storage/volumes.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/manuals/engine/storage/volumes.md b/content/manuals/engine/storage/volumes.md index 3f5838d67030..fb83dad96de0 100644 --- a/content/manuals/engine/storage/volumes.md +++ b/content/manuals/engine/storage/volumes.md @@ -403,9 +403,8 @@ $ docker volume rm nginx-vol ## Use a read-only volume -For some development applications, the container needs to write into the bind -mount so that changes are propagated back to the Docker host. At other times, -the container only needs read access to the data. Multiple +For some applications, the container needs to write to the volume. At other +times, the container only needs read access to the data. Multiple containers can mount the same volume. You can simultaneously mount a single volume as `read-write` for some containers and as `read-only` for others.