diff options
Diffstat (limited to 'docs/source')
| -rw-r--r-- | docs/source/markdown/podman-generate-kube.1.md | 3 | ||||
| -rw-r--r-- | docs/source/markdown/podman-play-kube.1.md | 2 |
2 files changed, 3 insertions, 2 deletions
diff --git a/docs/source/markdown/podman-generate-kube.1.md b/docs/source/markdown/podman-generate-kube.1.md index 8cd35140e..cbb875f60 100644 --- a/docs/source/markdown/podman-generate-kube.1.md +++ b/docs/source/markdown/podman-generate-kube.1.md @@ -22,7 +22,8 @@ Init containers created with type `always` will always be generated in the kube *Note*: When using volumes and generating a Kubernetes YAML for an unprivileged and rootless podman container on an **SELinux enabled system**, one of the following options must be completed: * Add the "privileged: true" option to the pod spec * Add `type: spc_t` under the `securityContext` `seLinuxOptions` in the pod spec - * Relabel the volume via the CLI command `chcon -t container_file_t context -R <directory>` + * Relabel the volume via the CLI command `chcon -t container_file_t -R <directory>` + Once completed, the correct permissions will be in place to access the volume when the pod/container is created in a Kubernetes cluster. Note that the generated Kubernetes YAML file can be used to re-run the deployment via podman-play-kube(1). diff --git a/docs/source/markdown/podman-play-kube.1.md b/docs/source/markdown/podman-play-kube.1.md index ad3bd421d..b959f6dd9 100644 --- a/docs/source/markdown/podman-play-kube.1.md +++ b/docs/source/markdown/podman-play-kube.1.md @@ -24,7 +24,7 @@ Only two volume types are supported by play kube, the *hostPath* and *persistent Note: When playing a kube YAML with init containers, the init container will be created with init type value `always`. -Note: *hostPath* volume types created by play kube will be given an SELinux private label (Z) +Note: *hostPath* volume types created by play kube will be given an SELinux shared label (z), bind mounts are not relabeled (use `chcon -t container_file_t -R <directory>`). Note: If the `:latest` tag is used, Podman will attempt to pull the image from a registry. If the image was built locally with Podman or Buildah, it will have `localhost` as the domain, in that case, Podman will use the image from the local store even if it has the `:latest` tag. |