WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available #12983
WARN[0000] The cgroupv2 manager is set to systemd but there is no systemd user session available #12983
https://github.com/containers/podman/issues/12983
rishubn opened on Jan 24, 2022 Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I am getting these warnings on pretty much every podman command. I am using debian bullseye with Systemd enabled Steps to reproduce the issue:
$ podman run –rm hello-world
Describe the results you received:
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
Describe the results you expected:
No warnings
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
$ podman version
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
Version: 3.0.1
API Version: 3.0.0
Go Version: go1.15.9
Built: Thu Jan 1 00:00:00 1970
OS/Arch: linux/arm64
Output of podman info –debug:
podman info –debug
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
host:
arch: arm64
buildahVersion: 1.19.6
cgroupManager: cgroupfs
cgroupVersion: v2
conmon:
package: ‘conmon: /usr/bin/conmon’
path: /usr/bin/conmon
version: ‘conmon version 2.0.25, commit: unknown’
cpus: 6
distribution:
distribution: debian
version: “11”
eventLogger: journald
hostname: obox
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 5.10.81-meson64
linkmode: dynamic
memFree: 2954960896
memTotal: 3875725312
ociRuntime:
name: crun
package: ‘crun: /usr/bin/crun’
path: /usr/bin/crun
version: |-
crun version 0.17
commit: 0e9229ae34caaebcb86f1fde18de3acaf18c6d9a
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
os: linux
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
selinuxEnabled: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: ‘slirp4netns: /usr/bin/slirp4netns’
version: |-
slirp4netns version 1.0.1
commit: 6a7b16babc95b6a3056b33fb45b74a6f62262dd4
libslirp: 4.4.0
swapFree: 1937858560
swapTotal: 1937858560
uptime: 24m 0.77s
registries:
search:
- docker.io
- quay.io store: configFile: /home/rishub/.config/containers/storage.conf containerStore: number: 0 paused: 0 running: 0 stopped: 0 graphDriverName: overlay graphOptions: overlay.mount_program: Executable: /usr/bin/fuse-overlayfs Package: ‘fuse-overlayfs: /usr/bin/fuse-overlayfs’ Version: |- fusermount3 version: 3.10.3 fuse-overlayfs: version 1.4 FUSE library version 3.10.3 using FUSE kernel interface version 7.31 graphRoot: /home/rishub/.local/share/containers/storage graphStatus: Backing Filesystem: extfs Native Overlay Diff: “false” Supports d_type: “true” Using metacopy: “false” imageStore: number: 1 runRoot: /run/user/1000/containers volumePath: /home/rishub/.local/share/containers/storage/volumes version: APIVersion: 3.0.0 Built: 0 BuiltTime: Thu Jan 1 00:00:00 1970 GitCommit: “” GoVersion: go1.15.9 OsArch: linux/arm64 Version: 3.0.1
Package info (e.g. output of rpm -q podman or apt list podman):
$ apt list podman Listing… Done podman/stable,now 3.0.1+dfsg1-3+b2 arm64 [installed] podman/stable 3.0.1+dfsg1-3+b2 armhf Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
No
Additional environment details (AWS, VirtualBox, physical, etc.): Armbian distribution on Odroid N2+ 5.10.81-meson64 kernel
Activity
openshift-ci added kind/bug Categorizes issue or PR as related to a bug. on Jan 24, 2022 rishubn rishubn commented on Jan 24, 2022 rishubn on Jan 24, 2022 Author Was fixed by installing the dbus-user-session package
rishubn closed this as completedon Jan 24, 2022
abitrolly mentioned this on Apr 16, 2022 Why podman needs dbus-user-session? #13895 abitrolly abitrolly commented on Apr 16, 2022 abitrolly on Apr 16, 2022 Contributor Installed dbus-user-session, but that didn’t fix the warnings on Debian 11.
AiyionPrime AiyionPrime commented on May 6, 2022 AiyionPrime on May 6, 2022 dbus-user-session is already installed, the usse is still there in Bullseye
abitrolly abitrolly commented on May 6, 2022 abitrolly on May 6, 2022 Contributor Had to reboot to make it work. Weird.
jdrowell jdrowell commented on Nov 19, 2022 jdrowell on Nov 19, 2022 · edited by jdrowell Had to reboot to make it work. Weird.
systemctl –user start dbus should work as well.
mbaroukh mbaroukh commented on Jan 8, 2023 mbaroukh on Jan 8, 2023 Just an information in case somebody in the same situation as me arrive here : I had the same problem but because I was sudoing to the user. Connecting my session directly to the target user removed the warnings.
dawosch dawosch commented on Apr 7, 2023 dawosch on Apr 7, 2023 Just an information in case somebody in the same situation as me arrive here : I had the same problem but because I was sudoing to the user. Connecting my session directly to the target user removed the warnings.
This is working, but is this the intened way?
heidemn mentioned this on Apr 22, 2023 Container restart fails with “address already in use” #9447
github-actions added locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. on Aug 28, 2023
github-actions locked as resolved and limited conversation to collaborators on Aug 28, 2023