% podman-pod-create(1)


podman-pod-create - Create a new pod


podman pod create [options]


Creates an empty pod, or unit of multiple containers, and prepares it to have containers added to it. The pod id is printed to STDOUT. You can then use podman create –pod <pod_id|pod_name> … to add containers to the pod, and podman pod start <pod_id|pod_name> to start the pod.



Add a host to the /etc/hosts file shared between all containers in the pod.


Path to cgroups under which the cgroup for the pod will be created. If the path is not absolute, the path is considered to be relative to the cgroups path of the init process. Cgroups will be created if they do not already exist.


Set custom DNS servers in the /etc/resolv.conf file that will be shared between all containers in the pod. A special option, “none” is allowed which disables creation of /etc/resolv.conf for the pod.


Set custom DNS options in the /etc/resolv.conf file that will be shared between all containers in the pod.


Set custom DNS search domains in the /etc/resolv.conf file that will be shared between all containers in the pod.


Print usage statement.


Set a hostname to the pod


Create an infra container and associate it with the pod. An infra container is a lightweight container used to coordinate the shared kernel namespace of a pod. Default: true.


Write the pid of the infra container’s conmon process to a file. As conmon runs in a separate process than Podman, this is necessary when using systemd to manage Podman containers and pods.


The command that will be run to start the infra container. Default: “/pause”.


The image that will be created for the infra container. Default: “k8s.gcr.io/pause:3.1”.


Set a static IP for the pod’s shared network.

-l, –label=label

Add metadata to a pod (e.g., –label com.example.key=value).


Read in a line delimited file of labels.


Set a static MAC address for the pod’s shared network.

-n, –name=name

Assign a name to the pod.


Set network mode for the pod. Supported values are bridge (the default), host (do not create a network namespace, all containers in the pod will use the host’s network), or a comma-separated list of the names of CNI networks the pod should join.


Disable creation of /etc/hosts for the pod.


Write the pod ID to the file.

-p, –publish=port

Publish a port or range of ports from the pod to the host.

Format: ip:hostPort:containerPort | ip::containerPort | hostPort:containerPort | containerPort Both hostPort and containerPort can be specified as a range of ports. When specifying ranges for both, the number of container ports in the range must match the number of host ports in the range. Use podman port to see the actual mapping: podman port CONTAINER $CONTAINERPORT.

NOTE: This cannot be modified once the pod is created.


If another pod with the same name already exists, replace and remove it. The default is false.


A comma delimited list of kernel namespaces to share. If none or “” is specified, no namespaces will be shared. The namespaces to choose from are ipc, net, pid, uts.

The operator can identify a pod in three ways: UUID long identifier (“f78375b1c487e03c9438c729345e54db9d20cfa2ac1fc3494b6eb60872e74778”) UUID short identifier (“f78375b1c487”) Name (“jonah”)

podman generates a UUID for each pod, and if a name is not assigned to the container with –name then a random string name will be generated for it. The name is useful any place you need to identify a pod.


$ podman pod create --name test

$ podman pod create --infra=false

$ podman pod create --infra-command /top

$ podman pod create --publish 8443:443




July 2018, Originally compiled by Peter Hunt pehunt@redhat.com