Ubuntu 24.04 & Podman restart bug
So I recently upgraded to Ubuntu 24.04.1 on my homelab NAS, and discovered that I could no longer restart any of my Podman containers. That is not…great, as I use autoupdates for most of my containers1.
There is also no fix for it, yet. Only a workaround :-)
It took me some time to discover why I couldn’t restart any containers after reboot, until I found this in the system log:
sep 08 08:15:08 atomic kernel: audit: type=1400 audit(1725776108.382:279172): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=420564 comm="3" requested_mask="receive" denied_mask="receive" signal=kill peer="crun"
sep 08 08:15:09 atomic podman[420567]: 2024-09-08 08:15:09.090202975 +0200 CEST m=+0.101909420 container health_status 509d35f31f1ca6f91193095f224ec1c664e961edd7d0410d773c14fae9641545 (image=docker.io/filebrowser/filebrowser:latest, name=syncthing_filebrowser, health_s[...]
sep 08 08:15:10 atomic kernel: audit: type=1400 audit(1725776110.178:279173): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=420591 comm="3" requested_mask="receive" denied_mask="receive" signal=term peer="crun"
sep 08 08:15:11 atomic podman[418962]: time="2024-09-08T08:15:11+02:00" level=warning msg="StopSignal SIGTERM failed to stop container 233e10251dc7-infra in 10 seconds, resorting to SIGKILL"
Update 2024-11-07 #
I just discovered that the issue seems to be fixed in Ubuntu, so no more shady PPAs needed!
To remove the PPA:
apt install ppa-purge
ppa-purge ppa:brightbox/experimental
ppa-purge didn’t remove the podman version installed through it, so I had to
remove it manually:
apt remove podman
apt autoremove
apt install podman
Not with tag
latest, I’m not insane! ↩︎