Package: podman
Version: 2.0.3+dfsg1-1
Followup-For: Bug #966093
Dear Robby and Maintainer,
to avoid the described failure in running podman *as a regular user*, it's
enough to execute the command:
$ echo 'runtime = "crun"' > ~/.config/containers/libpod.conf
afterwards, both
$ podman info
and
$ podman run -it debian:sid
work correctly.
As a side note, I think a note about the need for sysctl
kernel.unprivileged_userns_clone=1 should be present also in podman's
README.Debian, and not only in buildah's
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (777, 'testing'), (666, 'stable'), (333, 'oldstable'), (222,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.0.9-1
ii containernetworking-plugins 0.8.6-2
ii crun 0.14.1+dfsg-1
ii init-system-helpers 1.58
ii libc6 2.31-2
ii libdevmapper1.02.1 2:1.02.167-1+b1
ii libgpgme11 1.13.1-9
ii libseccomp2 2.4.3-1+b1
Versions of packages podman recommends:
ii buildah 1.15.0-4
ii fuse-overlayfs 1.0.0-1
ii slirp4netns 1.0.1-1
ii tini 0.18.0-1+b1
ii uidmap 1:4.8.1-1
Versions of packages podman suggests:
ii containers-storage 1.21.2+dfsg1-1
