*** This bug is a duplicate of bug 2065423 ***
https://bugs.launchpad.net/bugs/2065423
** This bug has been marked a duplicate of bug 2065423
Update AppArmor template to allow confined runc to kill containers
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Confirmed:
[Wed Oct 16 14:32:03 2024] audit: type=1400 audit(1729089123.317:127):
apparmor="DENIED" operation="signal" class="signal" profile="docker-default"
pid=2120 comm="runc" requested_mask="receive" denied_mask="receive" signal=quit
peer="runc"
[Wed Oct 16 14:32:05 2024] audit: type=1400
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079006
Title:
unable to stop docker daemon containers
To manage notifications about this bug go to:
https://bugs.launchpad.
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io-app (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079006
Title
