Your message dated Fri, 19 Aug 2022 08:35:14 +0000 with message-id <[email protected]> and subject line Bug#1007022: fixed in libpod 4.2.0+ds1-3 has caused the Debian Bug report #1007022, regarding podman: starting rootless container fails with: can't get final child's PID from pipe: EOF 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.) -- 1007022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007022 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: podman Version: 3.4.4+ds1-1 Severity: normal Hello, I used to be able to run rootless container on debian sid maybe 3 months ago (I'm sorry, I don't have much more precise information about versions when things used to work), but now that I try and start containers again I am consistently hitting errors of this form: $ podman run -d --name="draw" -p 8080:8080 -p 8443:8443 fjudith/draw.io Error: OCI runtime error: unable to start container "0f2eb8afb9ce6eebbede769dc288e228ea6cbae0e76936672e6673228ac6862c": runc create failed: unable to start container process: can't get final child's PID from pipe: EOF so no container will start at all in rootless mode for information, the images required for running the containers were correctly downloaded and are available locally. I've tried to search for information about this online but the cause for this particular error message can seemingly be very varied. The usual answers about the user.max_user_namespaces kernel option, or memory allocation settings for images/containers seem not to hold in this case. if I run the container as root with: # sudo podman run -d --name="draw" -p 8080:8080 -p 8443:8443 fjudith/draw.io then it's getting started as expected. I'm not sure what additional information could be helpful, but I'm willing to send more output from logs/commands to help out identify what's happening. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8), LANGUAGE not set 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 1.1.0+ds1-1 ii golang-github-containers-common 0.44.4+ds1-1 ii init-system-helpers 1.62 ii libc6 2.33-7 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.16.0-1.2 ii libseccomp2 2.5.3-2 ii runc 1.1.0+ds1-1 Versions of packages podman recommends: ii buildah 1.23.1+ds1-2 ii fuse-overlayfs 1.7.1-1 ii golang-github-containernetworking-plugin-dnsname 1.3.1+ds1-2 ii slirp4netns 1.0.1-2 ii tini 0.19.0-1 ii uidmap 1:4.11.1+dfsg1-2 Versions of packages podman suggests: pn containers-storage <none> ii docker-compose 1.29.2-1 ii iptables 1.8.7-1 -- Configuration Files: /etc/cni/net.d/87-podman-bridge.conflist [Errno 13] Permission denied: '/etc/cni/net.d/87-podman-bridge.conflist' -- no debconf information
--- End Message ---
--- Begin Message ---Source: libpod Source-Version: 4.2.0+ds1-3 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: Fri, 19 Aug 2022 09:43:54 +0200 Source: libpod Architecture: source Version: 4.2.0+ds1-3 Distribution: experimental Urgency: medium Maintainer: Debian Go Packaging Team <[email protected]> Changed-By: Reinhard Tartler <[email protected]> Closes: 1007022 1009376 1009747 1012053 Changes: libpod (4.2.0+ds1-3) experimental; urgency=medium . * Force using golang-go to avoid compilation failures with gcc-go * Confirmed updated components allow podman to work, thanks to Bastian Blank (Closes: #1012053), and is compiled against a containers/common that is more mindful regarding foreign-arch images (Closes: #1009376) * Confirmed fix: "starting rootless container fails with: can't get final child's PID from pipe: EOF", code change likely already in 4.1 thanks to Gabriel Filion (Closes: #1007022). * Make podman recommend 'dbus-user-session', Closes: #1009747 Checksums-Sha1: f5c12b2b1c48bff91bfd8f3c39072865acd2227d 5165 libpod_4.2.0+ds1-3.dsc 2cf38213403c79af777c22e9df70510f3e0ac4c0 15492 libpod_4.2.0+ds1-3.debian.tar.xz Checksums-Sha256: 09ec45ad17d3416e492c52fb46780de1bb47cc6ca326aee0b87f102b211f0a84 5165 libpod_4.2.0+ds1-3.dsc 14af6fe30656a99af08d1bb5ba1326e26029d116b462b13686f1b71ed0215eec 15492 libpod_4.2.0+ds1-3.debian.tar.xz Files: b4e5e4a321100a249aff7cd461db0d32 5165 admin optional libpod_4.2.0+ds1-3.dsc 7782167080adddbf14ddf1736029e8e1 15492 admin optional libpod_4.2.0+ds1-3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmL/QHIUHHNpcmV0YXJ0 QHRhdXdhcmUuZGUACgkQSadpd5QoJsvjBhAAmanfOiEAr1mUnygdYUHqLDt5b9xm diEWVCqtb7YRwDlk7r+PtAdxhnqA00Wk9nE9UPxh8f7mOfVh8gpyUugll22I5E43 Af4r84xm/8TXk5ekEVHBuf4R3ZeIGjBYbXSMW2HqtthNoFRjeSX60LJ09txFIe1C 62EJF9iOyH4dvFdjIGvsPE6bjvfEdRPiB4kINzw85DTRgOsdm3blqabycH9huYRz LZN86gwAhLI45Zx8KNqvnCH/HTMtWEZynUhelBZ+2vqdDIj7iOkStTiTov0bQLh8 izv0gBIuq/wPIFbHmupgJAk6YYdCQCOQ3ftsNZQ8xJv4/9RIkKtbfZYdzhDm9Hjm D+8MrcG18liKNlv1LWsD9Qi99OBjzqwmmwbH+nj08tgZSf0h66UjkaDN93+1+qI5 T23xf+NHA7VLSjwOp9XiMuNQI6KpTHJz4vO22/g09sNY2sjp6Sem2hMsdjTJRqmx Jc0yw6bo8L2Q6gvtVVz2xX3sc9qFltyWte6A61x1ytQ26M2NHamQPfqCDwWi0zXB BtoWFbDLPerIZ1gJsNS8bvUEqR4ne1GfjHVR/dxZmrt+Lmo2luxum6x7kpo16Qwi C7NyE5owyANpH+AwkJbcJrj59pL1KUzP7L39LKmN/6sOnRd5KQj0x3mGuMV0AXEn OCeDD93Egi1ax80= =0XwB -----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________ Pkg-go-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
