Your message dated Wed, 19 Apr 2023 21:17:08 +0000 with message-id <[email protected]> and subject line Bug#1018816: fixed in libpod 3.0.1+dfsg1-3+deb11u4 has caused the Debian Bug report #1018816, regarding podman operations generate warnings from bad parsing of DBUS_SESSION_BUS_ADDRESS to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1018816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018816 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: podman Version: 3.0.1+dfsg1-3+deb11u1 Severity: normal Tags: upstream Dear Maintainer, I have noticed that operations, such as 'podman ps' occationally print warning messages. Here is an example of this: paul@celebrimbor:~/git/podman (main)$ podman ps 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 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES paul@celebrimbor:~/git/podman (main)$ I tracked this problem down to the value of DBUS_SESSION_BUS_ADDRESS and how podman parses the value of this environment variable. It appears that this environment variable is (in general) a comma-separated list of key-value pairs, although I couldn't find a definitive statement on this in the DBUS specs. The podman code in the v3.0 branch (from which bullseye's v3.0.1 is tagged) assumes that the environment variable is a single key-value pair; i.e., that it contains no commas. This works fine sometimes; e.g., paul@celebrimbor:~$ echo $DBUS_SESSION_BUS_ADDRESS unix:path=/run/user/1000/bus paul@celebrimbor:~$ podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES paul@celebrimbor:~$ However, sometimes the DBUS_SESSION_BUS_ADDRESS value contains a 'guid' item; e.g., paul@celebrimbor:~/git/podman (main)$ echo $DBUS_SESSION_BUS_ADDRESS unix:path=/run/user/1000/bus,guid=5c5c86e60aa45c4c51dcfa0a630db85e paul@celebrimbor:~/git/podman (main)$ I haven't determined under what circumstances trigger the DBUS_SESSION_BUS_ADDRESS environment variable to contain this additional 'guid' item. Sometimes it's there and sometimes not. The presence of the 'guid' item causes some operations (e.g., 'podman ps') to issue the above warning. If the 'guid' item is removed then 'podman ps' works as expected: paul@celebrimbor:~/git/podman (main)$ echo $DBUS_SESSION_BUS_ADDRESS unix:path=/run/user/1000/bus,guid=5c5c86e60aa45c4c51dcfa0a630db85e paul@celebrimbor:~/git/podman (main)$ DBUS_SESSION_BUS_ADDRESS=$(echo $DBUS_SESSION_BUS_ADDRESS | cut -d, -f1) podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES paul@celebrimbor:~/git/podman (main)$ This problem appears to be specific to the podman version. In particular, it appears to have been fixed upstream with commit 732ece6ae2. This commit touches various parts of the code base. Fixing how the DBUS_SESSION_BUS_ADDRESS value is parsed is only one aspect of that change. Commit 732ece6ae2 is available from podman v3.3.0 onwards, but the change has not be back-ported to the earlier branches. Therefore, the v3.0 branch (from which v3.0.1 is tagged) contains this assumption about the DBUS_SESSION_BUS_ADDRESS value. I opened an issue against podman in github, requesting that the change be back-ported to the v3.0 branch: https://github.com/containers/podman/issues/15546 This would allow a new v3.0 release (v3.0.3) that Debian could adopt and resolve this issue. The issue was closed, requesting that I open a ticket here (against the Debian package) and that I cite the above issue as context. At the risk of pointing out the obvious, I would suggest there are four ways to resolve this issue: 1. Fix DBUS_SESSION_BUS_ADDRESS so it never includes the 'guid' value. 2. Pursuade upstream to back-port (part of) commit 732ece6ae2 to the v3.0 branch and make another release (v3.0.3) that Debian could adopt. 3. Patch the v3.0.1 source code (using part of commit 732ece6ae2) within the Debian build process. 4. Adopt a newer version of podman in bullseye. I see that bookworm is currently set to use v3.4.7. For me, this is a relatively minor problem, as I know how to work around it; however, it may cause others to waste time searching for a solution. Moreover, there are several web pages / forum posts that describe these symptoms but do not make a correct diagnostic about what is the underlying problem. Therefore, I think there is a risk that people may make unnecessary configuration changes or configure their system sub-optimally. Cheers, Paul. -- System Information: Debian Release: 11.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-17-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /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 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 ii runc 1.0.0~rc93+ds1-5+deb11u2 Versions of packages podman recommends: ii buildah 1.19.6+dfsg1-1+b6 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 tini 0.19.0-1 ii uidmap 1:4.8.1-1 Versions of packages podman suggests: pn containers-storage <none> pn docker-compose <none> -- Configuration Files: /etc/cni/net.d/87-podman-ptp.conflist [Errno 13] Permission denied: '/etc/cni/net.d/87-podman-ptp.conflist' -- no debconf information
--- End Message ---
--- Begin Message ---Source: libpod Source-Version: 3.0.1+dfsg1-3+deb11u4 Done: Reinhard Tartler <[email protected]> We believe that the bug you reported is fixed in the latest version of libpod, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler <[email protected]> (supplier of updated libpod package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 16 Apr 2023 18:16:11 -0400 Source: libpod Architecture: source Version: 3.0.1+dfsg1-3+deb11u4 Distribution: bullseye Urgency: medium Maintainer: Debian Go Packaging Team <[email protected]> Changed-By: Reinhard Tartler <[email protected]> Closes: 1018816 1020906 1020907 Changes: libpod (3.0.1+dfsg1-3+deb11u4) bullseye; urgency=medium . * Recompile to fix parsing of DBUS_SESSION_BUS_ADDRESS (Closes: #1018816) . libpod (3.0.1+dfsg1-3+deb11u3) bullseye; urgency=medium . * Fix and tighten dependencies . libpod (3.0.1+dfsg1-3+deb11u2) bullseye; urgency=medium . * CVE-2022-1227: pickup changes in containers/psgo, Closes: #1020907 * CVE-2022-27649: do not set the inheritable capabilities, Closes: #1020906 Checksums-Sha1: 9c5dccfa400387091e83c175bcbaf47380699a48 5032 libpod_3.0.1+dfsg1-3+deb11u4.dsc f2ec53c66d25681ca8860e1461fd589bba10c7fe 18320 libpod_3.0.1+dfsg1-3+deb11u4.debian.tar.xz Checksums-Sha256: 6ff3ead5390c895014fd39ea1a74b1653bf8d7cf458f4ee3b2798a244142ee88 5032 libpod_3.0.1+dfsg1-3+deb11u4.dsc dcc36991516c2a228149330aff987e739905a749b5d249ca0faae0db8ffc843c 18320 libpod_3.0.1+dfsg1-3+deb11u4.debian.tar.xz Files: b449ce025d4dfcbcdb5e78ea7a2b48cd 5032 admin optional libpod_3.0.1+dfsg1-3+deb11u4.dsc e89e833f5e50424bbcbca9e7624db4a4 18320 admin optional libpod_3.0.1+dfsg1-3+deb11u4.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmQ8dHoUHHNpcmV0YXJ0 QHRhdXdhcmUuZGUACgkQSadpd5QoJsuZKA//R/JX0frLjPCSSdJUySW0zrkv63Cg QkIXLnJY16VyrLS+C4itbRH4Uh+5tXceJlbRjyfrRqNaZ9T9vn6uGIo5zeYYFJR+ e7hfjP76vXWelsUyyqzUKzyP1neIqECjTfhrqO0FJVn3VFptT8cefNGd/HHbwToD BJZ3BWW1dj9SlRtRDm1hi48PmANFQwFraMAtrNl5eRbX4f9pUowpe7LZSMlY5Xz9 8sukQ/cCV1pK52/fS6HPWqLISH/MjETbIgRuCRUis6tMp+JvNvp8vVL/sUUv5UDl 7GtL+xTd3Z04CJ8Q4P7cPRWfIBuL1r83JiCwN4wEEbdjVlw8EQgyuJuET+sTHiaX 2HptOC8R4JTRN1JzlUNSGdiBaecT7LFpWbiNadpcZ9WdLb38u14xcBRhZsgKTpWV +PFbCcfS3pQ6Hlnm1gMGhtwESnqEhrxMEt21rbiZqxY2D+AVi4DA8YEtfWMuDhjP rDi5Qv3KyqQiBme3xJfy9UAR/J3opHJpAnd2SezrYfGwN7liQcGVvyrf/IDNVqpU El4QW8fxc3Gu+iLeOD4mDlYQfZ83nZK1scWmGYZcqG8qmP14QalZFBcaAEs+hsrT jhzFxnhYqfeVKEdCYqPs0y169R/O699vzs499/INkqD//ecw2AqPe0gfkEZsgP3N Co9MsFdmjI/Kwls= =m+MK -----END PGP SIGNATURE-----
--- End Message ---
