From e716790af9e81f8eae528e589379860d1cc60bf9 Mon Sep 17 00:00:00 2001 From: Federico Rizzo Date: Fri, 15 Apr 2022 21:51:30 +0000 Subject: Fix typo in generate kube docs for selinux labeling Signed-off-by: Federico Rizzo --- docs/source/markdown/podman-generate-kube.1.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs') 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 ` + * Relabel the volume via the CLI command `chcon -t container_file_t -R ` + 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). -- cgit v1.2.3-54-g00ecf