Public bug reported:
Cannot stop container running with default container-default AppArmor
profile
How to reproduce:
root@noble-test:~# podman run -d -e MARIADB_ALLOW_EMPTY_ROOT_PASSWORD=1 --name
mariadb docker.io/library/mariadb:latest
68b1c7b1daadc36526326cfffd86f2887ea2ddcc56cce440160c3e1dc2dd6d90
root@noble-test:~# podman stop mariadb
WARN[0010] StopSignal SIGTERM failed to stop container mariadb in 10 seconds,
resorting to SIGKILL
Error: given PID did not die within timeout
Workaround - use podman apparmor profile:
root@noble-test:~# podman run -d -e MARIADB_ALLOW_EMPTY_ROOT_PASSWORD=1
--security-opt=apparmor=podman --name mariadb-secopt
docker.io/library/mariadb:latest
b7fbace6fdba3fdd13a9463f3d9c332bc2105b2f0e83fa8d53b9ee7081558b9d
root@noble-test:~# podman stop mariadb-secopt
WARN[0010] StopSignal SIGTERM failed to stop container mariadb-secopt in 10
seconds, resorting to SIGKILL
mariadb-secopt
** Affects: libpod (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/2084230
Title:
24.04 podman and AppArmor - Error: given PID did not die within
timeout
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2084230/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
