> 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. Can you please try if this problem goes away with the podman 2.0 package from experimental? I can do 'podman run -it debian:sid' just fine with apparmor enabled, does triggering this bug require anything special? If it is still present, based on Dmitry's email I think this bug is better tracked in the 'crun' package. Best, -rt
