I followed the test plan for noble and got the following results: With docker.io 24.0.7-0ubuntu4.1 and containerd 1.7.12-0ubuntu4.1, I could not stop the container, as described in the test plan.
Installing the packages from noble-proposed, docker.io 26.1.3-0ubuntu1~24.04 and containerd 1.7.19-0ubuntu1~24.04, I got the following results: Before a system reboot, I could still not stop containers, although, changing the apparmor profile name passed as a parameter to containerd app, would result in allowing me to stop the container even before the reboot. After a system reboot, I could gracefully stop containers both for docker.io and containerd, as expected and described in the test plan. Neither jammy nor focal are affected by this bug, so I am removing the trackers for those from here and removing the SRU related tags as well. ** No longer affects: containerd-app (Ubuntu Jammy) ** No longer affects: containerd-app (Ubuntu Focal) ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065423 Title: Update AppArmor template to allow confined runc to kill containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2065423/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
