Your message dated Thu, 24 Nov 2022 21:05:07 +0000
with message-id <e1oyjp9-00ft4t...@fasolo.debian.org>
and subject line Bug#1007022: fixed in libpod 4.3.1+ds1-4
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 ow...@bugs.debian.org
immediately.)


-- 
1007022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007022
Debian Bug Tracking System
Contact ow...@bugs.debian.org 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.3.1+ds1-4
Done: Reinhard Tartler <siret...@tauware.de>

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 1007...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reinhard Tartler <siret...@tauware.de> (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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 24 Nov 2022 15:35:49 -0500
Source: libpod
Architecture: source
Version: 4.3.1+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintain...@lists.alioth.debian.org>
Changed-By: Reinhard Tartler <siret...@tauware.de>
Closes: 1000521 1001780 1003486 1006426 1007022 1009374 1009376 1009747 1012053 
1014309 1019591 1019929
Changes:
 libpod (4.3.1+ds1-4) unstable; urgency=medium
 .
   * upload to unstable
 .
 libpod (4.3.1+ds1-3) experimental; urgency=medium
 .
   * debian/rules: make the previous change to build machine/qemu only
     on supported architecture actually work
 .
 libpod (4.3.1+ds1-2) experimental; urgency=medium
 .
   * Build machine/qemu only on amd64, arm64, fixes FTBFS
 .
 libpod (4.3.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
     - Add container GID to additional groups,
       fixes CVE-2022-2989, closes: #1019591
   * Bugfix: Subordinate UID/GID ranges not fetched from libsubid,
     Thanks to Sam Morris <s...@robots.org.uk> for the patch, closes: #1019929
 .
 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
 .
 libpod (4.2.0+ds1-2) experimental; urgency=medium
 .
   * tighten dependency on golang-github-opencontainers-runc-dev
 .
 libpod (4.2.0+ds1-1) experimental; urgency=medium
 .
   * New upstream release
   * drop patches merged upstream
   * add distro patch to use system 'goimports' utility
   * tighten dependencies
   * hooks/docs no longer provides section 5 manpages
 .
 libpod (4.1.1+ds1-3) experimental; urgency=medium
 .
   * reorganize dependencies for networking stack
 .
 libpod (4.1.1+ds1-2) experimental; urgency=medium
 .
   * organize GOLANG_EXCLUDES and GOLANG_TEST_EXCLUDES
   * add patches fix-test-TestEnvVarValue-NN.patch, fixes
     Test failures for !amd64, !arm64 Closes: #1014309
 .
 libpod (4.1.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
 .
 libpod (4.1.0+ds2-2) experimental; urgency=medium
 .
   * Avoid building podman/pkg/machine/e2e on all architectures
 .
 libpod (4.1.0+ds2-1) experimental; urgency=medium
 .
   * New upstream release
 .
 libpod (4.0.3+ds1-1) experimental; urgency=medium
 .
   [ Antonio Terceiro ]
   * Stop installing systemd socket units under /usr/lib, Closes: #1009374
 .
   [ Reinhard Tartler ]
   * New upstream release
   * Skip installation of podman-remote(1), Closes: #1000521
 .
 libpod (4.0.1+ds1-3) experimental; urgency=medium
 .
   * Fix installation of systemd units
 .
 libpod (4.0.1+ds1-2) experimental; urgency=medium
 .
   * Install rootlessport, Closes: #1006426
 .
 libpod (4.0.1+ds1-1) experimental; urgency=medium
 .
   * New upstream release
 .
 libpod (4.0.0~rc5+ds1-1) experimental; urgency=medium
 .
   * New upstream release, closes: #1003486
   * Bug fix: "podman-restart missing from podman package", thanks to Jelle
     van der Waa (Closes: #1001780).
Checksums-Sha1:
 ca9b1623f5a9a9e33c37913a06fa3f8230655bf0 5179 libpod_4.3.1+ds1-4.dsc
 77698ceb9d050c6d64d51043144ca404e658bc09 16580 libpod_4.3.1+ds1-4.debian.tar.xz
Checksums-Sha256:
 d94b5335ec4c78845479a444c2abb26e90e954665bf05f88ebc26b65847574be 5179 
libpod_4.3.1+ds1-4.dsc
 7af6464fa5ae534dc4c87272fc6d13c9cee30119c215496e3d66f9d09daed28c 16580 
libpod_4.3.1+ds1-4.debian.tar.xz
Files:
 cdea8370086c360bfc09eafff95929dd 5179 admin optional libpod_4.3.1+ds1-4.dsc
 0c5bcec672844fe4539490409e6580ae 16580 admin optional 
libpod_4.3.1+ds1-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmN/1iUUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJssA2BAAwq6CV1nwgqR7NPHYkfoHd5Wo47HP
/lg1Nm/aeujuSpZn+DCT0VeAW2fgw8HUo5mWIeufpxWD/3ojdJRCOhwN20DJen8/
o9tLjzhxIg3VZ+0vNVggKQymvDaQCtBpe40kadDFANUKCbjbenzTKXvkQYRvjNHD
7Prnj/JQnSrRqDyzAIJ7EFsRgcFUEgEZG2tM8ieWMAOzZIeVopTt6P7cnuKlr8T7
QQF+bl8gVwdglrkyrjC6gQbwZYP+VSYfJpvbxp5Bie/aMW+N6rq8NJT1V5/tE5WP
SZvyOq0HrEhNU/B+JguLOGREuRpHoRanmzoRe8YuUIydApJuvu3IjneqlGP3JLHJ
TR9m03lWkzfJYJfQi9l64gKXCJ6WxdLTF16NIpyKCIf5kQySCooF/jP4xBu+zl+Y
78v/kXZxpXYO5sCBXQ9WSQ+xdGmtA0vfvdHYcSAeG8QSAeBZrl2J0G0kjaRJRdRm
6r0BzzmQQS0nucryveHVPSTR8CMooRwajVhWB1nZBr+oODrHMFp5X5JDKHqeSWYG
anoj4QBFYJ2HX1rs1IRzQ3bbmBHEz7Rdflb9Wp20fjejTrfVKjBZEj8YqmJC4zv9
c2QqJbcg67cxr7tkRtnDjdRhyiWpDjm4PWc3i37INdA+TbeiFWVEFvXZgE8rh1YZ
sv7PqK8U0omyX6k=
=1IVQ
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to