podman “The cgroupv2 manager is set to systemd but there is no systemd user session available” warning

https://superuser.com/questions/1788594/podman-the-cgroupv2-manager-is-set-to-systemd-but-there-is-no-systemd-user-sess

Asked 2 years, 6 months ago Modified 2 years, 4 months ago Viewed 10k times 5

Context I am using a Raspberry Pi running on Raspbian. I connect remotely using ssh. I want to use podman for building images and running containers, the exact same way I’ve done on my local machine. The installation of podman has been done the exact same way.

Issue Every time the podman command is used on the RPi, I get the following warning:

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 login using an 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
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 login using an 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 What I found I’ve found this GitHub issue which seems to be focusing on this warning, but I cannot understand what the underlying issue might be, and the solution they give (installing the dbus-user-session package) doesn’t seem to work, as it already is installed on my RPi.

What I need I’m not sure where this warning comes from and, although I cannot be sure of it, I suspect there might be some effects I have yet to see on the way the images are build/run/etc. I think it may be related to the users permission, but have no idea how to verify this.

Do any of you have an explanation?

raspberry-piraspbianpodman Share Improve this question Follow edited Jun 12, 2023 at 8:08 Destroy666’s user avatar Destroy666 15.6k1111 gold badges3737 silver badges7070 bronze badges asked Jun 12, 2023 at 7:20 GregoirePelegrin’s user avatar GregoirePelegrin 15111 silver badge33 bronze badges Add a comment 1 Answer Sorted by:

Highest score (default) 3

Try what podman suggests in the 3rd line (enabling lingering), which helped me on a related system with common ancestor (Ubuntu 22.04):

$ loginctl enable-linger $USER You can test if it worked by e.g.:

$ loginctl show-user “$USER” –property=Linger grep -q ‘yes’

a failure message would be: Failed to get user: User ID 1000 is not logged in or lingering

Share Improve this answer Follow answered Aug 5, 2023 at 11:37 mirekphd’s user avatar mirekphd 15788 bronze badges Maybe and/or reboot? Seemed to work for me, but I think I also enabled linger. – David Winiecki CommentedOct 2 at 2:40

Updated: