[pkg-go] Bug#1103560: podman: The cgroupv2 manager is set to systemd but there is no systemd user session available

[Reinhard Tartler]

Control: tag -1 moreinfo

Hi Andrew, thanks for filing this bug in debian.

andrew at lists.savchenko.net writes:

> 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>

What exactly is setting this environment variable to that value?

> However, for podman to work, it must be unix:path=/run/user/$(id -u)/bus

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

> [1]
> https://github.com/containers/podman/issues/8776#issuecomment-1237740241

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