diff options
| author | cdoern <cdoern@redhat.com> | 2021-09-01 10:59:23 -0400 |
|---|---|---|
| committer | cdoern <cdoern@redhat.com> | 2021-10-01 14:09:11 -0400 |
| commit | 6da97c86314d8c80b912ba83db57fd26da19bfb7 (patch) | |
| tree | 0e8e3de1d5eb89465b965458fb3068f59c702f34 /docs/source | |
| parent | e9d8524af5122314e47385299bf9ae3d0b000096 (diff) | |
| download | podman-6da97c86314d8c80b912ba83db57fd26da19bfb7.tar.gz podman-6da97c86314d8c80b912ba83db57fd26da19bfb7.tar.bz2 podman-6da97c86314d8c80b912ba83db57fd26da19bfb7.zip | |
Pod Volumes From Support
added support for a volumes from container. this flag just required movement of the volumes-from flag declaration
out of the !IsInfra block, and minor modificaions to container_create.go
Signed-off-by: cdoern <cdoern@redhat.com>
Diffstat (limited to 'docs/source')
| -rw-r--r-- | docs/source/markdown/podman-pod-create.1.md | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/docs/source/markdown/podman-pod-create.1.md b/docs/source/markdown/podman-pod-create.1.md index 4c36c66ca..08ac19b8b 100644 --- a/docs/source/markdown/podman-pod-create.1.md +++ b/docs/source/markdown/podman-pod-create.1.md @@ -381,6 +381,39 @@ change propagation properties of source mount. Say `/` is source mount for Note: if the user only has access rights via a group, accessing the volume from inside a rootless pod will fail. +#### **--volumes-from**[=*CONTAINER*[:*OPTIONS*]] + +Mount volumes from the specified container(s). Used to share volumes between +containers and pods. The *options* is a comma-separated list with the following available elements: + +* **rw**|**ro** +* **z** + +Mounts already mounted volumes from a source container into another +pod. You must supply the source's container-id or container-name. +To share a volume, use the --volumes-from option when running +the target container. You can share volumes even if the source container +is not running. + +By default, Podman mounts the volumes in the same mode (read-write or +read-only) as it is mounted in the source container. +You can change this by adding a `ro` or `rw` _option_. + +Labeling systems like SELinux require that proper labels are placed on volume +content mounted into a pod. Without a label, the security system might +prevent the processes running inside the container from using the content. By +default, Podman does not change the labels set by the OS. + +To change a label in the pod context, you can add `z` to the volume mount. +This suffix tells Podman to relabel file objects on the shared volumes. The `z` +option tells Podman that two entities share the volume content. As a result, +Podman labels the content with a shared content label. Shared volume labels allow +all containers to read/write content. + +If the location of the volume from the source container overlaps with +data residing on a target pod, then the volume hides +that data on the target. + ## EXAMPLES |