From c1de4d3ce28cbdd1ec5b57fed7d2059fc235c992 Mon Sep 17 00:00:00 2001 From: Valentin Rothberg Date: Mon, 24 Oct 2022 10:08:55 +0200 Subject: [PATCH] docs: kube play: mention restart policy Mention the default restart policy in the `kube play` docs. Fixes: #16252 Signed-off-by: Valentin Rothberg --- docs/source/markdown/podman-kube-play.1.md.in | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/source/markdown/podman-kube-play.1.md.in b/docs/source/markdown/podman-kube-play.1.md.in index a8f1b86106..e72248b70b 100644 --- a/docs/source/markdown/podman-kube-play.1.md.in +++ b/docs/source/markdown/podman-kube-play.1.md.in @@ -23,6 +23,8 @@ Currently, the supported Kubernetes kinds are: Only three volume types are supported by kube play, the *hostPath*, *emptyDir*, and *persistentVolumeClaim* volume types. For the *hostPath* volume type, only the *default (empty)*, *DirectoryOrCreate*, *Directory*, *FileOrCreate*, *File*, *Socket*, *CharDevice* and *BlockDevice* subtypes are supported. Podman interprets the value of *hostPath* *path* as a file path when it contains at least one forward slash, otherwise Podman treats the value as the name of a named volume. When using a *persistentVolumeClaim*, the value for *claimName* is the name for the Podman named volume. When using an *emptyDir* volume, podman creates an anonymous volume that is attached the containers running inside the pod and is deleted once the pod is removed. +Note: The default restart policy for containers is `always`. You can change the default by setting the `restartPolicy` field in the spec. + Note: When playing a kube YAML with init containers, the init container will be created with init type value `once`. To change the default type, use the `io.podman.annotations.init.container.type` annotation to set the type to `always`. Note: *hostPath* volume types created by kube play will be given an SELinux shared label (z), bind mounts are not relabeled (use `chcon -t container_file_t -R `).