Podman is an alternative to Docker, providing a similar interface.
Unlike Docker, Podman does not require a daemon, but there is one providing an API for services like via .
By default it is only possible to run Podman containers as root. See Rootless Podman to set up running containers as a non-root user.
Configuration files for configuring how containers behave are located at
/etc/containers. To configure the network bridge interface used by Podman see
By default only
root is allowed to run containers (or namespaces in kernelspeak).
kernel.unprivileged_userns_cloneis set to
0(but rootless podman requires it to be set to
1). Use sysctl or a kernel parameter to configure it.
To allow rootless operation of Podman containers, first determine which user(s) and group(s) you want to use for the containers, and then add their corresponding entries to
The following example enables the
podman user and group to run Podman containers (or other types of containers in that case). It allocates the UIDs and GIDs from 165536 to 169631 to the
podman user and group respectively. This can be achieved either by editing these files directly or with . See and for more information.
# usermod --add-subuids 165536-231072 --add-subgids 165536-231072 podman
After this the user/group
podman is able to start and run podman containers.
registries.searchin the defined order. The following images will always contain the prefix, to allow for configurations without
docker.ioin the configuration.
# podman pull docker.io/archlinux
See also README.md.
For a full Arch base, clone the repo from above and build your own image.
Make sure that thepackage is installed.
packages file so it only contains 'base'. Then run:
# make rootfs # podman build -t archlinux .
# podman pull docker.io/alpine
Alpine Linux uses the musl libc implementation instead of the glibc libc implementation used by most Linux distributions. Because Arch Linux uses glibc, there are a number of functional differences between an Arch Linux host and an Alpine Linux container that can impact the performance and correctness of software. A list of these differences is documented in https://wiki.musl-libc.org/functional-differences-from-glibc.html.
Note that dynamically linked software built on Arch Linux (or any other system using glibc) may have bugs and performance problems when run on Alpine Linux (or any other system using a different libc). See ,  and  for examples.
# podman pull docker.io/centos
See the Docker Hub page for a full list of available tags for each CentOS release.
# podman pull docker.io/debian
See the Docker Hub page for a full list of available tags, including both standard and slim versions for each Debian release.