#1103560 podman: The cgroupv2 manager is set to systemd but there is no systemd user session available

Package:
podman
Source:
podman
Description:
tool to manage containers and pods
Submitter:
Date:
2026-04-08 10:27:02 UTC
Severity:
normal
Tags:
#1103560#5
Date:
2025-04-19 03:52:24 UTC
From:
To:
Podman shows the following warning when trying to (start|stop) a container:
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

#1103560#10
Date:
2025-09-22 09:57:26 UTC
From:
To:
Hi Andrew, thanks for filing this bug in debian.

andrew@lists.savchenko.net writes:

What exactly is setting this environment variable to that value?

That is what the variable is set on my machines, and I haven't changed
anything special.

That comment refers to a related, but very different situation. Here, the
person asking ended up with an "abstract" path in $DBUS_SESSION_BUS_ADDRESS,
which is not working for podman.

As far as I can tell, this behavior seems intentional with upstream. If
you are arguing podman should also work with "abstract" and "guid" path
specifications, I need to ask you to bringt this up upstream.


Best,
-rt

#1103560#19
Date:
2026-04-08 10:25:06 UTC
From:
To:
Can't be reproduced on Podman v5.4.2 / Debian 13.4