Podman - ArchWiki

Tags

Top Highlights

• /etc/containers/registries.conf.d/00-unqualified-search-registries.conf unqualified-search-registries = ["docker.io"] /etc/containers/registries.conf.d/01-registries.conf [[registry]] location = "docker.io"

• This affects containers which use chroot (like archlinux:base) and thus pacman operations fail within the container (i.e. installing packages which execute post-install scripts). You can identify such issues if when building with podman you get errors like below during build: ... could not change the root directory (Operation not permitted) error: command failed to execute correctly ...

• from the command line temporarily with --cap-add sys_chroot when you execute podman-build(1).

• Set the driver according to the filesystem in use for the storage location (see containers-storage.conf(5) § STORAGE_TABLE).

• Podman is able to run images built for different CPU architecture than the host using the Wikipedia:binfmt_misc system. To enable it, install qemu-user-static and qemu-user-static-binfmt.

• get hostname resolution between containers running install podman-dnsname

• If you have enabled buildkit in docker, the integration will not work.

• .io

• 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.

• use the full registry path in the Containerfile or Dockerfile.

• shared

• The slirp4netns package is installed as a dependency to run Podman in a rootless environment.

• If Podman uses the netavark network backend (see containers.conf(5)) then it is required to install aardvark-dns to have name resolution in rootless containers.

• Install the podman package.

• Additionally if you want to build container images look at Buildah.

• /usr/share/containers/. You must copy necessary files to /etc/containers before editing

• configure the network bridge interface used by Podman, see /etc/cni/net.d/87-podman.conflist

• First, check the value of kernel.unprivileged_userns_clone by running: $ sysctl kernel.unprivileged_userns_clone

• In order for users to run rootless Podman, a subuid(5) and subgid(5) configuration entry must exist for each user that wants to use it.

• usermod --add-subuids 100000-165535 --add-subgids 100000-165535