Thanks for providing the workaround Tomáš! I can confirm that it works
in Noble, but for me, even using the profile you provided in comment #4,
the command below takes more or less 10 seconds (against 12 seconds when
the containers are killed with SIGKILL):

root@docker-apparmor:~# time docker stop $(docker run --rm -d nginx)
81948b000a5510fe4d59c476d783c7f4d8946f86ffa916d4b317678c74b54ffb

real    0m12.538s
user    0m0.015s
sys     0m0.027s
[ ... download profile from comment #4 ... ]
root@docker-apparmor:~# apparmor_parser -Kr /etc/apparmor.d/docker-default
root@docker-apparmor:~# time docker stop $(docker run --rm -d nginx)
ef2b4c117fa48954288c418d80088ce88fc5233fc13a7084003cb5c980e42369

real    0m10.563s
user    0m0.016s
sys     0m0.027s
root@docker-apparmor:~# time docker stop $(docker run --rm -d nginx)
a8ab8186872d856368ad4b627fa36fa5b0fff78ac5f6ddc9db3e0545f744b741

real    0m10.514s
user    0m0.011s
sys     0m0.031s
root@docker-apparmor:~# time docker stop $(docker run --rm -d nginx)
42d8afedec05f31ba1999ffbad2e7696eaf295f150e3b5f26a8e5e3cd27a2406

real    0m10.503s
user    0m0.019s
sys     0m0.024s

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063099

Title:
  Stopping container signal blocked by AppArmor on Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/2063099/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to