diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2022-06-09 17:13:31 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-06-09 17:13:31 -0400 |
| commit | 9f1bd0a0a1494f46a49ca7f22511c5a78006afd8 (patch) | |
| tree | 6975686d75ddf58c6ee8881e2807e941aedc68b7 /docs/source/markdown/podman-build.1.md | |
| parent | f808907d85204a2a5606067eb31400aa12233635 (diff) | |
| parent | c0ad9a43e4baffec7f217c327ff1c6004843bdd9 (diff) | |
| download | podman-9f1bd0a0a1494f46a49ca7f22511c5a78006afd8.tar.gz podman-9f1bd0a0a1494f46a49ca7f22511c5a78006afd8.tar.bz2 podman-9f1bd0a0a1494f46a49ca7f22511c5a78006afd8.zip | |
Merge pull request #14405 from rhatdan/docs
[CI:DOCS] Mount propagation works with named volumes
Diffstat (limited to 'docs/source/markdown/podman-build.1.md')
| -rw-r--r-- | docs/source/markdown/podman-build.1.md | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/docs/source/markdown/podman-build.1.md b/docs/source/markdown/podman-build.1.md index 4d6a74a1f..25c0121f8 100644 --- a/docs/source/markdown/podman-build.1.md +++ b/docs/source/markdown/podman-build.1.md @@ -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 be visible only inside of the container. To control the mount propagation property of volume use the `:[r]shared`, `:[r]slave` or `:[r]private` -propagation flag. The propagation property can be specified only for bind mounted -volumes and not for internal volumes or named volumes. For mount propagation to -work on the source mount point (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 has to be either -shared or slave. <sup>[[1]](#Footnote1)</sup> +propagation flag. For mount propagation to work on the source mount point (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 has to be either shared or slave. <sup>[[1]](#Footnote1)</sup> Use `df <source-dir>` to determine the source mount and then use `findmnt -o TARGET,PROPAGATION <source-mount-dir>` to determine propagation |