Hey folks, I've managed to test the new packages (installing
podman/noble-proposed and golang-github-containers-common/noble-
proposed) and can confirm everything is now working.
I used this command to test:
```
$ sudo podman run --rm -d --name nginx nginx
```
Originally when trying to stop this container, I would get this error:
```
$ sudo podman stop nginx
WARN[0010] StopSignal SIGQUIT failed to stop container nginx in 10 seconds,
resorting to SIGKILL
Error: given PID did not die within timeout
```
Running PS I would see the processes still running:
```
$ ps auxww | grep nginx
root 152857 0.0 0.0 14776 2432 ? Ss 16:21 0:00
/usr/bin/conmon --api-version 1 -c
2ccdab29bc75f3d7a2e1cba9aa7d438142da565f12f18c6dc9f53442a8f8b70b -u
2ccdab29bc75f3d7a2e1cba9aa7d438142da565f12f18c6dc9f53442a8f8b70b -r
/usr/bin/crun -b
/var/lib/containers/storage/overlay-containers/2ccdab29bc75f3d7a2e1cba9aa7d438142da565f12f18c6dc9f53442a8f8b70b/userdata
-p
/run/containers/storage/overlay-containers/2ccdab29bc75f3d7a2e1cba9aa7d438142da565f12f18c6dc9f53442a8f8b70b/userdata/pidfile
-n nginx --exit-dir /run/libpod/exits --full-attach -s -l journald --log-level
warning --syslog --runtime-arg --log-format=json --runtime-arg --log
--runtime-arg=/run/containers/storage/overlay-containers/2ccdab29bc75f3d7a2e1cba9aa7d438142da565f12f18c6dc9f53442a8f8b70b/userdata/oci-log
--conmon-pidfile
/run/containers/storage/overlay-containers/2ccdab29bc75f3d7a2e1cba9aa7d438142da565f12f18c6dc9f53442a8f8b70b/userdata/conmon.pid
--exit-command /usr/bin/podman --exit-command-arg --root --exit-command-arg
/var/lib/containers/storage --exit-command-arg --runroot --exit-command-arg
/run/containers/storage --exit-command-arg --log-level --exit-command-arg
warning --exit-command-arg --cgroup-manager --exit-command-arg systemd
--exit-command-arg --tmpdir --exit-command-arg /run/libpod --exit-command-arg
--network-config-dir --exit-command-arg --exit-command-arg --network-backend
--exit-command-arg netavark --exit-command-arg --volumepath --exit-command-arg
/var/lib/containers/storage/volumes --exit-command-arg --db-backend
--exit-command-arg boltdb --exit-command-arg --transient-store=false
--exit-command-arg --runtime --exit-command-arg crun --exit-command-arg
--events-backend --exit-command-arg journald --exit-command-arg container
--exit-command-arg cleanup --exit-command-arg --rm --exit-command-arg
2ccdab29bc75f3d7a2e1cba9aa7d438142da565f12f18c6dc9f53442a8f8b70b
root 152859 0.2 0.1 11128 7040 ? Ss 16:21 0:00 nginx:
master process nginx -g daemon off;
usbmux 152895 0.0 0.0 11588 2864 ? S 16:21 0:00 nginx:
worker process
usbmux 152896 0.0 0.0 11588 2864 ? S 16:21 0:00 nginx:
worker process
usbmux 152897 0.0 0.0 11588 2864 ? S 16:21 0:00 nginx:
worker process
usbmux 152898 0.0 0.0 11588 2864 ? S 16:21 0:00 nginx:
worker process
matthew 152998 0.0 0.0 9272 1920 pts/0 S+ 16:21 0:00 grep nginx
```
I would have to manually kill the nginx processes to try to stop the
container, but it would still appear as stopping, like this:
```
$ sudo podman ps -a
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
2ccdab29bc75 docker.io/library/nginx:latest nginx -g daemon o... About a
minute ago Stopping nginx
```
After the upgrade, I was able to stop the container:
```
$ sudo podman stop nginx
nginx
$ sudo podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
```
I can also confirm that there are no longer any nginx processes running,
so the container has been stopped 100% successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppArmor denies crun sending signals to containers (stop, kill)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
