From c0ad9a43e4baffec7f217c327ff1c6004843bdd9 Mon Sep 17 00:00:00 2001 From: Daniel J Walsh Date: Sat, 28 May 2022 07:06:16 -0400 Subject: Mount propagation works with named volumes Fixes: https://github.com/containers/podman/issues/13939 Signed-off-by: Daniel J Walsh --- docs/source/markdown/podman-create.1.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) (limited to 'docs/source/markdown/podman-create.1.md') diff --git a/docs/source/markdown/podman-create.1.md b/docs/source/markdown/podman-create.1.md index 009209343..2da902844 100644 --- a/docs/source/markdown/podman-create.1.md +++ b/docs/source/markdown/podman-create.1.md @@ -1404,12 +1404,10 @@ will be visible inside container but not the other way around. [[1]](#Footn To control mount propagation property of a volume one can use the [**r**]**shared**, [**r**]**slave**, [**r**]**private** or the [**r**]**unbindable** propagation flag. -Propagation property can be specified only for bind mounted volumes and not for -internal volumes or named volumes. For mount propagation to work the source mount -point (the mount point where source dir is mounted on) has to have the right propagation -properties. For shared volumes, the source mount point has to be shared. And for -slave volumes, the source mount point has to be either shared or slave. -[[1]](#Footnote1) +For mount propagation to work the source mount point (the mount point where source dir +is mounted on) has to have the right propagation properties. For shared volumes, the +source mount point has to be shared. And for slave volumes, the source mount point +has to be either shared or slave. [[1]](#Footnote1) If you want to recursively mount a volume and all of its submounts into a container, then you can use the `rbind` option. By default the bind option is -- cgit v1.2.3-54-g00ecf