Important to note that this bug is a sure way to corrupt user data in production environments.
E.g. databases running in Docker containers have no clue that they're being asked to shut down gracefully, because of blocked signals. When under load, a database would be forcefully killed with SIGKILL in the middle of flushing data to disk, which leads to partial data writes, corrupting data files. In dev environments the bug also annoyingly introduces guaranteed 10 sec delays on container restarts or stops. I guess most of 'docker.io' package users on 24.04 noticed this bug (observing slow stops), but the root cause is obscure enough to prevent them from finding the appropriate bug report to weigh in. Please prioritize the backport to Noble, the bug is there since Oct 2023 and the fix is in upstream since May 2024. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
