Package: podman Version: 5.4.2+ds1-1 The podman package maintainer scripts will stop podman systemd services during a package update but never restart them afterwards.
This is surprising for administrators that have enabled any of these services either manually or from a previous version that had them enabled by default. Administrators will now see podman services stop every time a podman package update happens and will have to restart them manually. The services remain enabled so a reboot would also restart them. If a service is running at package update time it should remain running afterwards. This behavior was introduced in 5.4.1+ds1-1. Here is an example of enabling a podman service and simulating a package update: --------------- $ sudo apt install podman Installing: podman Suggested packages: docker-compose Summary: Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 1 Download size: 24.7 MB Space needed: 87.5 MB / 5797 MB available Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B] Get:2 https://deb.debian.org/debian trixie/main amd64 podman amd64 5.4.2+ds1-1 [24.7 MB] Fetched 24.7 MB in 0s (51.4 MB/s) Selecting previously unselected package podman. (Reading database ... 76310 files and directories currently installed.) Preparing to unpack .../podman_5.4.2+ds1-1_amd64.deb ... Unpacking podman (5.4.2+ds1-1) ... Setting up podman (5.4.2+ds1-1) ... Processing triggers for man-db (2.13.0-1) ... $ systemctl status podman.socket ○ podman.socket - Podman API Socket Loaded: loaded (/usr/lib/systemd/system/podman.socket; disabled; preset: enabled) Active: inactive (dead) Triggers: ● podman.service Docs: man:podman-system-service(1) Listen: /run/podman/podman.sock (Stream) $ sudo systemctl enable --now podman.socket Created symlink '/etc/systemd/system/sockets.target.wants/podman.socket' → '/usr/lib/systemd/system/podman.socket'. $ systemctl status podman.socket ● podman.socket - Podman API Socket Loaded: loaded (/usr/lib/systemd/system/podman.socket; enabled; preset: enabled) Active: active (listening) since Thu 2025-05-01 11:29:25 UTC; 2s ago Invocation: ff25332b735d4f5ab92ae30a9c53d19c Triggers: ● podman.service Docs: man:podman-system-service(1) Listen: /run/podman/podman.sock (Stream) CGroup: /system.slice/podman.socket $ sudo apt install podman --reinstall Summary: Upgrading: 0, Installing: 0, Reinstalling: 1, Removing: 0, Not Upgrading: 1 Download size: 24.7 MB Space needed: 0 B / 5708 MB available Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B] Get:2 https://deb.debian.org/debian trixie/main amd64 podman amd64 5.4.2+ds1-1 [24.7 MB] Fetched 24.7 MB in 0s (54.4 MB/s) (Reading database ... 76595 files and directories currently installed.) Preparing to unpack .../podman_5.4.2+ds1-1_amd64.deb ... Unpacking podman (5.4.2+ds1-1) over (5.4.2+ds1-1) ... Setting up podman (5.4.2+ds1-1) ... Processing triggers for man-db (2.13.0-1) ... $ systemctl status podman.socket ○ podman.socket - Podman API Socket Loaded: loaded (/usr/lib/systemd/system/podman.socket; enabled; preset: enabled) Active: inactive (dead) since Thu 2025-05-01 11:29:42 UTC; 9s ago Duration: 17.258s Invocation: ff25332b735d4f5ab92ae30a9c53d19c Triggers: ● podman.service Docs: man:podman-system-service(1) Listen: /run/podman/podman.sock (Stream)
