Your message dated Wed, 8 Apr 2026 20:25:06 +1000
with message-id <[email protected]>
and subject line Bug #1103560: closing - fixed
has caused the Debian Bug report #1103560,
regarding podman: The cgroupv2 manager is set to systemd but there is no
systemd user session available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1103560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103560
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: podman
Version: 5.4.2+ds1-1
Severity: normal
Podman shows the following warning when trying to (start|stop) a container:
----------------------------------------------------
WARN[0000] The cgroupv2 manager is set to systemd but there is no
systemd user session available
WARN[0000] For using systemd, you may need to log in using a user session
WARN[0000] Alternatively, you can enable lingering with: `loginctl
enable-linger 1000` (possibly as root)
WARN[0000] Falling back to --cgroup-manager=cgroupfs
----------------------------------------------------
As noted in this [1] comment:
By default, $DBUS_SESSION_BUS_ADDRESS is set to
unix:path=/tmp/dbus-<RANDOM>,guid=<RANDOM>
However, for podman to work, it must be unix:path=/run/user/$(id -u)/bus
[1] https://github.com/containers/podman/issues/8776#issuecomment-1237740241
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.21-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.1.12-4
ii crun 1.21-1
ii golang-github-containers-common 0.62.2+ds1-2
ii init-system-helpers 1.68
ii libc6 2.41-6
ii libgpgme11t64 1.24.2-1+b1
ii libseccomp2 2.6.0-2
ii libsqlite3-0 3.46.1-3
ii libsubid5 1:4.17.4-1
ii netavark 1.14.0-2
ii runc 1.1.15+ds1-2+b2
Versions of packages podman recommends:
ii buildah 1.39.3+ds1-1+b1
ii ca-certificates 20241223
ii catatonit 0.2.1-1
ii containers-storage 1.57.2+ds1-1
ii criu 4.1-1
ii dbus-user-session 1.16.2-2
ii libcriu2 4.1-1
ii passt 0.0~git20250320.32f6212-1
ii slirp4netns 1.2.1-1+b1
ii uidmap 1:4.17.4-1
Versions of packages podman suggests:
ii containernetworking-plugins 1.1.1+ds1-3+b15
ii docker-compose 2.26.1-4
ii iptables 1.8.11-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.4.2
Can't be reproduced on Podman v5.4.2 / Debian 13.4
--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
