Package: podman Version: 1.6.4+dfsg1-3 Severity: important Dear Maintainer,
When I run "podman exec ..." on a running container, it always fails: $ sudo podman exec 8791af6116b9 ps Error: AppArmor not initialized correctly: OCI runtime error (This is a multi-process container running systemd; I don't know if that makes a difference to the behaviour.) I was able to work around this by adding "apparmor=0" to the kernel command line. Ben. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages podman depends on: ii conmon 2.0.9-1 ii containernetworking-plugins 0.8.5-1 ii crun 0.13+dfsg-1 ii libc6 2.30-8 ii libdevmapper1.02.1 2:1.02.167-1+b1 ii libgpgme11 1.13.1-6 ii libseccomp2 2.4.3-1+b1 Versions of packages podman recommends: ii buildah 1.11.6-1 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: pn containers-storage <none> -- no debconf information -- Ben Hutchings, Software Developer Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street Manchester, M1 2HF, United Kingdom
