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

[Elias Batek]

Package: podman
Version: 3.0.1+dfsg1-3+deb11u1
Severity: minor
X-Debbugs-Cc: e.batek+debian at itkaufmann.at

Dear Maintainer,

   * What led up to the situation?

Podman, in the default installation, spits out a lot of warning messages.
I couln’t find any information on that regard in the wiki[0].

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

$ sudo apt install podman
$ podman search --limit 3 quay.io/podman

   * What was the outcome of this action?

> 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 outcome did you expect instead?

No warning with no further configuration.

I’ve found a kinda related upstream issue[1].
Is setting `cgroup_manager = "cgroupfs"`, as suggested along the upstream bug report, a reasonable configuration on Debian?

Best regards,
Elias


-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-0.bpo.1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
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.0.25+ds1-1.1
ii  containernetworking-plugins      0.9.0-1+b6
ii  crun                             0.17+dfsg-1
ii  golang-github-containers-common  0.33.4+ds1-1+deb11u1
ii  init-system-helpers              1.60
ii  iptables                         1.8.7-1
ii  libc6                            2.31-13+deb11u3
ii  libdevmapper1.02.1               2:1.02.175-2.1
ii  libgpgme11                       1.14.0-1+b2
ii  libseccomp2                      2.5.1-1+deb11u1

Versions of packages podman recommends:
ii  buildah                                           1.19.6+dfsg1-1+b6
ii  catatonit                                         0.1.5-2
ii  fuse-overlayfs                                    1.4.0-1
ii  golang-github-containernetworking-plugin-dnsname  1.1.1+ds1-4+b7
ii  slirp4netns                                       1.0.1-2
ii  uidmap                                            1:4.8.1-1

Versions of packages podman suggests:
pn  containers-storage  <none>
pn  docker-compose      <none>

-- no debconf information


[0] https://wiki.debian.org/Podman
[1] https://github.com/containers/podman/issues/5906#issuecomment-1079587477