% podman-play-kube(1)


podman-play-kube - Create pods and containers based on Kubernetes YAML


podman play kube [options] file.yml


podman play kube will read in a structured file of Kubernetes YAML. It will then recreate the pod and containers described in the YAML. The containers within the pod are then started and the ID of the new Pod is output.

Ideally the input file would be one created by Podman (see podman-generate-kube(1)). This would guarantee a smooth import and expected results.

Note: HostPath volume types created by play kube will be given an SELinux private label (Z)



Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/containers/auth.json, which is set using podman login. If the authorization state is not found there, $HOME/.docker/config.json is checked, which is set using docker login. (Not available for remote commands)

Note: You can also override the default path of the authentication file by setting the REGISTRY_AUTH_FILE environment variable. export REGISTRY_AUTH_FILE=path


Use certificates at path (*.crt, *.cert, *.key) to connect to the registry. Default certificates directory is /etc/containers/certs.d. (Not available for remote commands)


The [username[:password]] to use to authenticate with the registry if required. If one or both values are not supplied, a command line prompt will appear and the value can be entered. The password is entered without echo.

–network=cni networks

A comma-separated list of the names of CNI networks the pod should join.

–quiet, -q

Suppress output information when pulling images


Directory path for seccomp profiles (default: “/var/lib/kubelet/seccomp”). (Not available for remote commands)


Require HTTPS and verify certificates when contacting registries (default: true). If explicitly set to true, then TLS verification will be used. If set to false, then TLS verification will not be used. If not specified, TLS verification will be used unless the target registry is listed as an insecure registry in registries.conf. (Not available for remote commands)

–help, -h

Print usage statement


Recreate the pod and containers as described in a file called demo.yml

$ podman play kube demo.yml

CNI network(s) can be specified as comma-separated list using --network

$ podman play kube demo.yml --network cni1,cni2

Please take into account that CNI networks must be created first using podman-network-create(1).


podman(1), podman-container(1), podman-pod(1), podman-generate-kube(1), podman-play(1), podman-network-create(1)


December 2018, Originally compiled by Brent Baude (bbaude at redhat dot com)