Skip to content

Commit 7b65eab

Browse files
committed
storage: remove mention of "named volumes" for mount propagation
Mount propagation is not supported for named volumes, as mentioned in the paragraph before this one, so let's remove it here. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
1 parent f7c9499 commit 7b65eab

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

storage/bind-mounts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -284,7 +284,7 @@ only configurable for bind mounts, and only on Linux host machines. Bind
284284
propagation is an advanced topic and many users never need to configure it.
285285

286286
Bind propagation refers to whether or not mounts created within a given
287-
bind-mount or named volume can be propagated to replicas of that mount. Consider
287+
bind-mount can be propagated to replicas of that mount. Consider
288288
a mount point `/mnt`, which is also mounted on `/tmp`. The propagation settings
289289
control whether a mount on `/tmp/a` would also be available on `/mnt/a`. Each
290290
propagation setting has a recursive counterpoint. In the case of recursion,

0 commit comments

Comments
 (0)