This worked to remove the profile: # echo -n containers-default-0.57.4 > /sys/kernel/security/apparmor/.remove
Then of course all running podman containers become unconfined. You can at least stop them, and any new ones you start from now on, the first one will trigger the load of the updated apparmor profile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
