Your message dated Fri, 19 Aug 2022 08:35:14 +0000
with message-id <[email protected]>
and subject line Bug#1009376: fixed in libpod 4.2.0+ds1-3
has caused the Debian Bug report #1009376,
regarding running foreign architecture containers hits the network every time
and confuses future `podman run` invocations
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.)
--
1009376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009376
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: podman
Version: 3.4.4+ds1-1
Severity: normal
When running containers for a foreign architecture, podman run will hit
the networking looking for images on every invocation:
----------------8<----------------8<----------------8<-----------------
terceiro@host:~$ podman run --arch=arm64 debian arch
Resolved "debian" as an alias
(/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull docker.io/library/debian:latest...
Getting image source signatures
Copying blob fa223d8c149d done
Copying config 05e8051d05 done
Writing manifest to image destination
Storing signatures
aarch64
terceiro@host:~$ podman run --arch=arm64 debian arch
Resolved "debian" as an alias
(/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull docker.io/library/debian:latest...
Getting image source signatures
Copying blob fa223d8c149d [-----------------] 0.0b / 0.0b
Copying config 05e8051d05 done
Writing manifest to image destination
Storing signatures
aarch64
----------------8<----------------8<----------------8<-----------------
This means that if I try run a foreign container while I'm offline, I
can't:
----------------8<----------------8<----------------8<-----------------
terceiro@host:~$ podman run --arch=arm64 debian arch
Resolved "debian" as an alias
(/etc/containers/registries.conf.d/shortnames.conf)
Trying to pull docker.io/library/debian:latest...
Error: initializing source docker://debian:latest: pinging container registry
registry-1.docker.io: Get "https://registry-1.docker.io/v2/": dial tcp: lookup
registry-1.docker.io on 10.0.2.3:53: dial udp 10.0.2.3:53: connect: network is
unreachable
----------------8<----------------8<----------------8<-----------------
Weirder than that, is that from this point on, a plain `podman run` will
run the foreign container, instead of a native one (but will not hit the
network, as I'm able to do that while still offline):
----------------8<----------------8<----------------8<-----------------
terceiro@host:~$ podman run debian arch
aarch64
----------------8<----------------8<----------------8<-----------------
To "fix" this, I have to explicitly pull the same image without any
architecture request after coming online again:
----------------8<----------------8<----------------8<-----------------
terceiro@host:~$ podman pull debian
Trying to pull docker.io/library/debian:latest...
Getting image source signatures
Copying blob dbba69284b27 done
Copying config d69c6cd3a2 done
Writing manifest to image destination
Storing signatures
d69c6cd3a20d21ec91b677c3bcd10d9975f4fe67eff81afb5a09bdef5134afeb
terceiro@host:~$ podman run debian arch
x86_64
----------------8<----------------8<----------------8<-----------------
I have checked the version in experimental, and this bug still applies
to it.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (500,
'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
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 1.1.0+ds1-1
ii crun 0.17+dfsg-1.1
ii golang-github-containers-common 0.47.2+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.1+ds1-1
Versions of packages podman recommends:
ii buildah 1.24.1+ds1-1
ii catatonit 0.1.7-1
ii fuse-overlayfs 1.8.2-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
-- no debconf information
signature.asc
Description: PGP signature
--- 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
