podman - Simple management tool for pods, containers and images
podman [options] command
Podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool.
Podman provides a Docker-CLI comparable command line that eases the transition from other
container engines and allows the management of pods, containers and images. Simply put:
Most Podman commands can be run as a regular user, without requiring additional
Podman uses Buildah(1) internally to create container images. Both tools share image (not container) storage, hence each can use or manipulate images (but not containers) created by the other.
Default settings for flags are defined in
containers.conf. Most settings for
Remote connections use the server’s containers.conf, except when documented in
podman [GLOBAL OPTIONS]
The CGroup manager to use for container cgroups. Supported values are cgroupfs or systemd. Default is systemd unless overridden in the containers.conf file.
Note: Setting this flag can cause certain commands to break when called on containers previously created by the other CGroup manager type. Note: CGroup manager is not supported in rootless mode when using CGroups Version V1.
Path to the directory where network configuration files are located. For the CNI backend the default is “/etc/cni/net.d” as root and “$HOME/.config/cni/net.d” as rootless. For the netavark backend “/etc/containers/networks” is used as root and “$graphroot/networks” as rootless.
Connection to use for remote podman (Default connection is configured in
Remote connections use local containers.conf for default.
Path of the conmon binary (Default path is configured in
Backend to use for storing events. Allowed values are file, journald, and none. When file is specified, the events are stored under a subdirectory of the tmpdir location (see --tmpdir below).
Print usage statement
*.json file in the path configures a hook for Podman containers. For more details on the syntax of the JSON files and the semantics of hook injection, see
oci-hooks(5). Podman and libpod currently support both the 1.0.0 and 0.1.0 hook schemas, although the 0.1.0 schema is deprecated.
This option may be set multiple times; paths from later options have higher precedence (
oci-hooks(5) discusses directory precedence).
For the annotation conditions, libpod uses any annotations set in the generated OCI configuration.
For the bind-mount conditions, only mounts explicitly requested by the caller via
--volume are considered. Bind mounts that libpod inserts by default (e.g.
/dev/shm) are not considered.
--hooks-dir is unset for root callers, Podman and libpod will currently default to
/etc/containers/oci/hooks.d in order of increasing precedence. Using these defaults is deprecated, and callers should migrate to explicitly setting
Podman and libpod currently support an additional
precreate state which is called before the runtime’s
create operation. Unlike the other stages, which receive the container state on their standard input,
precreate hooks receive the proposed runtime configuration on their standard input. They may alter that configuration as they see fit, and write the altered form to their standard output.
precreate hook lets you do powerful things, such as adding additional mounts to the runtime configuration. That power also makes it easy to break things. Before reporting libpod errors, try running your container with
precreate hooks disabled to see if the problem is due to one of your hooks.
Path to ssh identity file. If the identity file has been encrypted, podman prompts the user for the passphrase. If no identity file is provided and no user is given, podman defaults to the user running the podman command. Podman prompts for the login password on the remote server.
Identity value resolution precedence:
command line value
containers.confRemote connections use local containers.conf for default.
Log messages at and above specified level: debug, info, warn, error, fatal or panic (default: “warn”)
Set libpod namespace. Namespaces are used to separate groups of containers and pods in libpod’s state. When namespace is set, created containers and pods will join the given namespace, and only containers and pods in the given namespace will be visible to Podman.
Path to the command binary to use for setting up a network. It is currently only used for setting up a slirp4netns network. If “” is used then the binary is looked up using the $PATH environment variable.
Redirect stdout to /dev/null. This command will prevent all stdout from the Podman command. The --noout option will not block stderr or stdout from containers.
When true, access to the Podman service will be remote. Defaults to false. Settings can be modified in the containers.conf file. If the CONTAINER_HOST environment variable is set, the remote option defaults to true.
URL to access Podman service (default from
unix://run/user/$UID/podman/podman.sock or as root
CONTAINER_HOSTis of the format
userwill default to either
rootor current running user
passwordhas no default
hostmust be provided and is either the IP or name of the machine hosting the Podman service
portdefaults to 22
pathdefaults to either
/run/user/<uid>/podman/podman.sockif running rootless.
URL value resolution precedence:
command line value
unix://run/podman/podman.sockRemote connections use local containers.conf for default.
Storage root dir in which data, including images, is stored (default: “/var/lib/containers/storage” for UID 0, “$HOME/.local/share/containers/storage” for other users).
Default root dir configured in
Overriding this option will cause the storage-opt settings in /etc/containers/storage.conf to be ignored. The user must specify additional options via the
Storage state directory where all state information is stored (default: “/run/containers/storage” for UID 0, “/run/user/$UID/run” for other users).
Default state dir configured in
Name of the OCI runtime as specified in containers.conf or absolute path to the OCI compatible binary used to run containers.
Adds global flags for the container runtime. To list the supported flags, please
consult the manpages of the selected container runtime (
runc is the default
runtime, the manpage to consult is
runc(8). When the machine is configured
for cgroup V2, the default runtime is
crun, the manpage to consult is
Note: Do not pass the leading
-- to the flag. To pass the runc flag
to podman build, the option given would be
Storage driver. The default storage driver for UID 0 is configured in /etc/containers/storage.conf (
$HOME/.config/containers/storage.conf in rootless mode), and is vfs for non-root users when fuse-overlayfs is not available. The
STORAGE_DRIVER environment variable overrides the default. The --storage-driver specified driver overrides all.
Overriding this option will cause the storage-opt settings in /etc/containers/storage.conf to be ignored. The user must
specify additional options via the
Storage driver option, Default storage driver options are configured in /etc/containers/storage.conf (
$HOME/.config/containers/storage.conf in rootless mode). The
STORAGE_OPTS environment variable overrides the default. The --storage-opt specified options overrides all. If you specify --storage-opt=””, no storage options will be used.
Output logging information to syslog as well as the console (default false).
On remote clients, logging is directed to the file $HOME/.config/containers/podman.log.
Path to the tmp directory, for libpod runtime content.
NOTE --tmpdir is not used for the temporary storage of downloaded images. Use the environment variable
TMPDIR to change the temporary storage location of downloaded container images. Podman defaults to use
Print the version
Podman can set up environment variables from env of [engine] table in containers.conf. These variables can be overridden by passing environment variables before the
Set default locations of containers.conf file
Set default location of the registries.conf file.
Set default location of the storage.conf file.
--connection value to access Podman service. Also enabled --remote option.
--url value to access Podman service. Also enabled --remote option.
--identity path to ssh key file value used to access Podman service.
Set the temporary storage location of downloaded container images. Podman defaults to use
In Rootless mode configuration files are read from
specified, otherwise in the home directory of the user under
In Rootless mode images are pulled under
XDG_DATA_HOME when specified,
otherwise in the home directory of the user under
In Rootless mode temporary configuration data is stored in
The Podman command can be used with remote services using the
--remote flag. Connections can
be made using local unix domain sockets, ssh or directly to tcp sockets. When specifying the
podman --remote flag, only the global options
--connection are used.
Connection information can also be managed using the containers.conf file.
The exit code from
podman gives information about why the container
failed to run or why it exited. When
podman commands exit with a non-zero code,
the exit codes follow the
chroot standard, see below:
125 The error is with podman itself
$ podman run --foo busybox; echo $? Error: unknown flag: --foo 125
126 Executing a contained command and the command cannot be invoked
$ podman run busybox /etc; echo $? Error: container_linux.go:346: starting container process caused "exec: \"/etc\": permission denied": OCI runtime error 126
127 Executing a contained command and the command cannot be found $ podman run busybox foo; echo $? Error: container_linux.go:346: starting container process caused “exec: “foo”: executable file not found in $PATH”: OCI runtime error 127
Exit code contained command exit code
$ podman run busybox /bin/sh -c 'exit 3'; echo $? 3
Attach to a running container.
Auto update containers according to their auto-update policy
Build a container image using a Containerfile.
Create new image based on the changed container.
Generate shell completion scripts
Copy files/folders between a container and the local filesystem.
Create a new container.
Inspect changes on a container or image’s filesystem.
Monitor Podman events
Execute a command in a running container.
Export a container’s filesystem contents as a tar archive.
Generate structured data based on containers, pods or volumes.
Manage healthchecks for containers
Show the history of an image.
List images in local storage.
Import a tarball and save it as a filesystem image.
Displays Podman related system information.
Initialize one or more containers
Display a container, image, volume, network, or pod’s configuration.
Kill the main process in one or more containers.
Load image(s) from a tar archive into container storage.
Login to a container registry.
Logout of a container registry.
Display the logs of one or more containers.
Manage Podman’s virtual machine
Create and manipulate manifest lists and image indexes.
Mount a working container’s root filesystem.
Manage Podman CNI networks.
Pause one or more containers.
Play containers, pods or volumes based on a structured input file.
Management tool for groups of containers, called pods.
List port mappings for a container.
Prints out information about containers.
Pull an image from a registry.
Push an image, manifest list or image index from local storage to elsewhere.
Rename an existing container.
Restart one or more containers.
Remove one or more containers.
Removes one or more locally stored images.
Run a command in a new container.
Save image(s) to an archive.
Search a registry for an image.
Manage podman secrets.
Start one or more containers.
Display a live stream of one or more container’s resource usage statistics.
Stop one or more running containers.
Add an additional name to a local image.
Display the running processes of a container.
Unmount a working container’s root filesystem.
Unpause one or more containers.
Run a command inside of a modified user namespace.
Removes one or more names from a locally-stored image.
Display the Podman version information.
Simple management tool for volumes.
Wait on one or more containers to stop and print their exit codes.
Podman has builtin defaults for command line options. These defaults can be overridden using the containers.conf configuration files.
Distributions ship the
/usr/share/containers/containers.conf file with their default settings. Administrators can override fields in this file by creating the
/etc/containers/containers.conf file. Users can further modify defaults by creating the
$HOME/.config/containers/containers.conf file. Podman merges its builtin defaults with the specified fields from these files, if they exist. Fields specified in the users file override the administrator’s file, which overrides the distribution’s file, which override the built-in defaults.
Podman uses builtin defaults if no containers.conf file is found.
If the CONTAINERS_CONF environment variable is set, then its value is used for the containers.conf file rather than the default.
The mounts.conf file specifies volume mount directories that are automatically mounted inside containers when executing the
podman run or
podman start commands. Administrators can override the defaults file by creating
When Podman runs in rootless mode, the file
$HOME/.config/containers/mounts.conf will override the default if it exists. Please refer to containers-mounts.conf(5) for further details.
Signature verification policy files are used to specify policy, e.g. trusted keys, applicable when deciding whether to accept an image, or individual signatures of that image, as valid.
registries.conf is the configuration file which specifies which container registries should be consulted when completing image names which do not include a registry or domain portion.
Non root users of Podman can create the
$HOME/.config/containers/registries.conf file to be used instead of the system defaults.
If the CONTAINERS_REGISTRIES_CONF environment variable is set, then its value is used for the registries.conf file rather than the default.
storage.conf is the storage configuration file for all tools using containers/storage
The storage configuration file specifies all of the available container storage options for tools using shared container storage.
When Podman runs in rootless mode, the file
$HOME/.config/containers/storage.conf is used instead of the system defaults.
If the CONTAINERS_STORAGE_CONF environment variable is set, then its value is used for the storage.conf file rather than the default.
Podman can also be used as non-root user. When podman runs in rootless mode, a user namespace is automatically created for the user, defined in /etc/subuid and /etc/subgid.
Containers created by a non-root user are not visible to other users and are not seen or managed by Podman running as root.
It is required to have multiple uids/gids set for a user. Be sure the user is present in the files
If you have a recent version of usermod, you can execute the following commands to add the ranges to the files
$ sudo usermod --add-subuids 10000-75535 USERNAME $ sudo usermod --add-subgids 10000-75535 USERNAME
Or just add the content manually.
$ echo USERNAME:10000:65536 >> /etc/subuid $ echo USERNAME:10000:65536 >> /etc/subgid
subgid(5) man pages for more information.
Images are pulled under
XDG_DATA_HOME when specified, otherwise in the home directory of the user under
Currently the slirp4netns package is required to be installed to create a network device, otherwise rootless containers need to run in the network namespace of the host.
In certain environments like HPC (High Performance Computing), users cannot take advantage of the additional UIDs and GIDs from the /etc/subuid and /etc/subgid systems. However, in this environment, rootless Podman can operate with a single UID. To make this work, set the
ignore_chown_errors option in the /etc/containers/storage.conf or in ~/.config/containers/storage.conf files. This option tells Podman when pulling an image to ignore chown errors when attempting to change a file in a container image to match the non-root UID in the image. This means all files get saved as the user’s UID. Note this could cause issues when running the container.
NOTE: Unsupported file systems in rootless mode¶
The Overlay file system (OverlayFS) is not supported with kernels prior to 5.12.9 in rootless mode. The fuse-overlayfs package is a tool that provides the functionality of OverlayFS in user namespace that allows mounting file systems in rootless environments. It is recommended to install the fuse-overlayfs package. In rootless mode, Podman will automatically use the fuse-overlayfs program as the mount_program if installed, as long as the $HOME/.config/containers/storage.conf file was not previously created. If storage.conf exists in the homedir, add
mount_program = "/usr/bin/fuse-overlayfs" under
[storage.options.overlay] to enable this feature.
The Network File System (NFS) and other distributed file systems (for example: Lustre, Spectrum Scale, the General Parallel File System (GPFS)) are not supported when running in rootless mode as these file systems do not understand user namespace. However, rootless Podman can make use of an NFS Homedir by modifying the
$HOME/.config/containers/storage.conf to have the
graphroot option point to a directory stored on local (Non NFS) storage.
For more information, please refer to the Podman Troubleshooting Page.
containers-mounts.conf(5), containers.conf(5), containers-registries.conf(5), containers-storage.conf(5), buildah(1), oci-hooks(5), containers-policy.json(5), crun(1), runc(8), subuid(5), subgid(5), slirp4netns(1), conmon(8)
Dec 2016, Originally compiled by Dan Walsh mailto:firstname.lastname@example.org