I tested the fix, it's actually ready to sponsor, but I don't know how real deployments out there could use this fix once it's available.
The profile is not a file on disk, it's inside the podman binary. There is nothing reloading the fixed profile when the package is upgraded or installed, it's only loaded when a container is created. But if I start a new container with the new podman, it also won't load the new fixed apparmor profile: it will use the one that is already loaded into the kernel (the wrong one). Without resorting to a reboot, how would one apply this fix to a live system? -- 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
