Public bug reported: On noble (works on jammy), when starting a daemon container, running docker stop always ends up in killing the process.
Found a bug but it was reported to: - apparmor (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2039294) - docker.io (not docker.io-app) https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/2063099 Decided to file a bug here to ensure it targets the right maintainers. Apparently, bug is known and fixed in upstream since april: https://github.com/moby/moby/issues/47720 https://github.com/moby/moby/pull/47749/commits/5ebe2c0d6bf30ad76550f0dc8cf35a71098ba5fc Steps to reproduce: * use a fresh install of noble * install docker.io * docker run --name nginx -d nginx * docker stop nginx * docker logs nginx => no signal was received * docker container inspect --format '{{json .State}}' nginx reports exit with 137 {"Status":"exited","Running":false,"Paused":false,"Restarting":false,"OOMKilled":false,"Dead":false,"Pid":0,"ExitCode":137,"Error":"","StartedAt":"2024-09-04T20:03:44.977090442Z","FinishedAt":"2024-09-04T20:04:44.899930911Z"} Note that: - doing alike on jammy works like a charm - deploying docker-default apparmor profile referenced in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2039294 fixes issue and confirms this is related to runc missing permissions to send signals to process containers - it may affect latest Ubuntu versions (after noble): haven't tested ** Affects: docker.io-app (Ubuntu) Importance: Undecided Status: New -- 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.net/ubuntu/+source/docker.io-app/+bug/2079006/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
