opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-05-21 17:16:22 +08:00
Code Issues Packages Projects Releases Wiki Activity

Mount propagation works with named volumes

Browse Source 
Fixes: https://github.com/containers/podman/issues/13939

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
This commit is contained in:
Daniel J Walsh
2022-05-28 07:06:16 -04:00
parent a550af260a
commit c0ad9a43e4
4 changed files with 18 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/source/markdown/podman-build.1.md
View File

@ -913,12 +913,10 @@ container. When the mount propagation policy is set to `slave`, one way mount
propagation is enabled and any mounts completed on the host for that volume will propagation is enabled and any mounts completed on the host for that volume will
be visible only inside of the container. To control the mount propagation be visible only inside of the container. To control the mount propagation
property of volume use the `:[r]shared`, `:[r]slave` or `:[r]private` property of volume use the `:[r]shared`, `:[r]slave` or `:[r]private`
propagation flag. The propagation property can be specified only for bind mounted propagation flag. For mount propagation to work on the source mount point (mount
volumes and not for internal volumes or named volumes. For mount propagation to point where source dir is mounted on) has to have the right propagation properties.
work on the source mount point (mount point where source dir is mounted on) has For shared volumes, the source mount point has to be shared. And for slave volumes,
to have the right propagation properties. For shared volumes, the source mount the source mount has to be either shared or slave. <sup>[[1]](#Footnote1)</sup>
point has to be shared. And for slave volumes, the source mount has to be either
shared or slave. <sup>[[1]](#Footnote1)</sup>
Use `df <source-dir>` to determine the source mount and then use Use `df <source-dir>` to determine the source mount and then use
`findmnt -o TARGET,PROPAGATION <source-mount-dir>` to determine propagation `findmnt -o TARGET,PROPAGATION <source-mount-dir>` to determine propagation

10
docs/source/markdown/podman-create.1.md
View File

@ -1404,12 +1404,10 @@ will be visible inside container but not the other way around. <sup>[[1]](#Footn
To control mount propagation property of a volume one can use the [**r**]**shared**, To control mount propagation property of a volume one can use the [**r**]**shared**,
[**r**]**slave**, [**r**]**private** or the [**r**]**unbindable** propagation flag. [**r**]**slave**, [**r**]**private** or the [**r**]**unbindable** propagation flag.
Propagation property can be specified only for bind mounted volumes and not for For mount propagation to work the source mount point (the mount point where source dir
internal volumes or named volumes. For mount propagation to work the source mount is mounted on) has to have the right propagation properties. For shared volumes, the
point (the mount point where source dir is mounted on) has to have the right propagation source mount point has to be shared. And for slave volumes, the source mount point
properties. For shared volumes, the source mount point has to be shared. And for has to be either shared or slave. <sup>[[1]](#Footnote1)</sup>
slave volumes, the source mount point has to be either shared or slave.
<sup>[[1]](#Footnote1)</sup>
If you want to recursively mount a volume and all of its submounts into a 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 container, then you can use the `rbind` option. By default the bind option is

10
docs/source/markdown/podman-pod-create.1.md
View File

@ -467,12 +467,10 @@ will be visible inside container but not the other way around. <sup>[[1]](#Footn
To control mount propagation property of a volume one can use the [**r**]**shared**, To control mount propagation property of a volume one can use the [**r**]**shared**,
[**r**]**slave**, [**r**]**private** or the [**r**]**unbindable** propagation flag. [**r**]**slave**, [**r**]**private** or the [**r**]**unbindable** propagation flag.
Propagation property can be specified only for bind mounted volumes and not for For mount propagation to work the source mount point (the mount point where source dir
internal volumes or named volumes. For mount propagation to work the source mount is mounted on) has to have the right propagation properties. For shared volumes, the
point (the mount point where source dir is mounted on) has to have the right propagation source mount point has to be shared. And for slave volumes, the source mount point
properties. For shared volumes, the source mount point has to be shared. And for has to be either shared or slave. <sup>[[1]](#Footnote1)</sup>
slave volumes, the source mount point has to be either shared or slave.
<sup>[[1]](#Footnote1)</sup>
If you want to recursively mount a volume and all of its submounts into a If you want to recursively mount a volume and all of its submounts into a
pod, then you can use the `rbind` option. By default the bind option is pod, then you can use the `rbind` option. By default the bind option is

14
docs/source/markdown/podman-run.1.md
View File

@ -1473,14 +1473,12 @@ visible on host and vice versa. Making a volume **slave** enables only one
way mount propagation and that is mounts done on host under that volume way mount propagation and that is mounts done on host under that volume
will be visible inside container but not the other way around. <sup>[[1]](#Footnote1)</sup> will be visible inside container but not the other way around. <sup>[[1]](#Footnote1)</sup>
To control mount propagation property of volume one can use [**r**]**shared**, To control mount propagation property of a volume one can use the [**r**]**shared**,
[**r**]**slave**, [**r**]**private** or [**r**]**unbindable** propagation flag. [**r**]**slave**, [**r**]**private** or the [**r**]**unbindable** propagation flag.
Propagation property can be specified only for bind mounted volumes and not for For mount propagation to work the source mount point (the mount point where source dir
internal volumes or named volumes. For mount propagation to work source mount is mounted on) has to have the right propagation properties. For shared volumes, the
point (mount point where source dir is mounted on) has to have right propagation source mount point has to be shared. And for slave volumes, the source mount point
properties. For shared volumes, source mount point has to be shared. And for has to be either shared or slave. <sup>[[1]](#Footnote1)</sup>
slave volumes, source mount has to be either shared or slave.
<sup>[[1]](#Footnote1)</sup>
If you want to recursively mount a volume and all of its submounts into a 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 container, then you can use the **rbind** option. By default the bind option is