Bug#989803: podman 3.0.1 rootless network issues: Connection reset by peer
Hi! Thanks for the fast reaction: I build it and can confirm that it solves the issue! Best regards, Alexander Am 2021-06-14 00:33, schrieb Reinhard Tartler: Hi Alexander, thank you for reporting this issue. I've prepared a fix for this that adds the referenced commit as a distro patch. Can you please try to build https://salsa.debian.org/debian/libpod/-/merge_requests/4 and let me know if that fixes the issue? Thanks! On Sun, Jun 13, 2021 at 12:27 PM Alexander Reichle-Schmehl wrote: Hi! Found a minimal example at https://stackoverflow.com/questions/67049585/how-to-publish-ports-in-user-defined-network-in-rootless-podman To reproduce: $ podman network create samplenet $ podman network ls NAME VERSION PLUGINS samplenet 0.4.0bridge,portmap,firewall,tuning,dnsname $ podman run -dt --name test --network=samplenet --rm --publish 8080:80 nginx $ podman port -l 80/tcp -> 0.0.0.0:8080 $ curl localhost:8080 curl: (56) Recv failure: Connection reset by peer Best regards, Alexander Am 2021-06-13 18:01, schrieb Alexander Reichle-Schmehl: Package: podman Version: 3.0.1+dfsg1-2+b2 Severity: important Tags: patch upstream X-Debbugs-Cc: alexan...@alphamar.org Running podman containers rootless seems I was unable to access any network services in a container. The apps work inside the container, but not from the host system. Searching around I found https://github.com/containers/podman/issues/9532 which seems to be the isse I run into. The bug log also mentiones a missing patch in 3.0.1. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US: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 ii containernetworking-plugins 0.9.0-1+b5 ii crun 0.17+dfsg-1 ii golang-github-containers-common 0.33.4+ds1-1 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc62.31-12 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.14.0-1+b2 ii libseccomp2 2.5.1-1 Versions of packages podman recommends: ii buildah 1.19.6+dfsg1-1+b4 ii catatonit 0.1.5-2 ii fuse-overlayfs1.4.0-1 ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b6 ii slirp4netns 1.0.1-2 ii uidmap1:4.8.1-1 Versions of packages podman suggests: pn containers-storage pn docker-compose -- no debconf information -- regards, Reinhard
Bug#989803: podman 3.0.1 rootless network issues: Connection reset by peer
Hi Alexander, thank you for reporting this issue. I've prepared a fix for this that adds the referenced commit as a distro patch. Can you please try to build https://salsa.debian.org/debian/libpod/-/merge_requests/4 and let me know if that fixes the issue? Thanks! On Sun, Jun 13, 2021 at 12:27 PM Alexander Reichle-Schmehl < alexan...@alphamar.org> wrote: > Hi! > > Found a minimal example at > > https://stackoverflow.com/questions/67049585/how-to-publish-ports-in-user-defined-network-in-rootless-podman > > To reproduce: > > $ podman network create samplenet > $ podman network ls > NAME VERSION PLUGINS > samplenet 0.4.0bridge,portmap,firewall,tuning,dnsname > $ podman run -dt --name test --network=samplenet --rm --publish 8080:80 > nginx > $ podman port -l > 80/tcp -> 0.0.0.0:8080 > $ curl localhost:8080 > curl: (56) Recv failure: Connection reset by peer > > > Best regards, >Alexander > > > Am 2021-06-13 18:01, schrieb Alexander Reichle-Schmehl: > > Package: podman > > Version: 3.0.1+dfsg1-2+b2 > > Severity: important > > Tags: patch upstream > > X-Debbugs-Cc: alexan...@alphamar.org > > > > Running podman containers rootless seems I was unable to access any > > network services in a container. > > The apps work inside the container, but not from the host system. > > > > Searching around I found > > https://github.com/containers/podman/issues/9532 which seems to be the > > isse I run into. > > The bug log also mentiones a missing patch in 3.0.1. > > > > > > -- System Information: > > Debian Release: 11.0 > > APT prefers testing-security > > APT policy: (500, 'testing-security'), (500, 'testing') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > > LANGUAGE=en_US: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 > > ii containernetworking-plugins 0.9.0-1+b5 > > ii crun 0.17+dfsg-1 > > ii golang-github-containers-common 0.33.4+ds1-1 > > ii init-system-helpers 1.60 > > ii iptables 1.8.7-1 > > ii libc62.31-12 > > ii libdevmapper1.02.1 2:1.02.175-2.1 > > ii libgpgme11 1.14.0-1+b2 > > ii libseccomp2 2.5.1-1 > > > > Versions of packages podman recommends: > > ii buildah 1.19.6+dfsg1-1+b4 > > ii catatonit 0.1.5-2 > > ii fuse-overlayfs1.4.0-1 > > ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b6 > > ii slirp4netns 1.0.1-2 > > ii uidmap1:4.8.1-1 > > > > Versions of packages podman suggests: > > pn containers-storage > > pn docker-compose > > > > -- no debconf information > > -- regards, Reinhard
Bug#989803: podman 3.0.1 rootless network issues: Connection reset by peer
Hi! Found a minimal example at https://stackoverflow.com/questions/67049585/how-to-publish-ports-in-user-defined-network-in-rootless-podman To reproduce: $ podman network create samplenet $ podman network ls NAME VERSION PLUGINS samplenet 0.4.0bridge,portmap,firewall,tuning,dnsname $ podman run -dt --name test --network=samplenet --rm --publish 8080:80 nginx $ podman port -l 80/tcp -> 0.0.0.0:8080 $ curl localhost:8080 curl: (56) Recv failure: Connection reset by peer Best regards, Alexander Am 2021-06-13 18:01, schrieb Alexander Reichle-Schmehl: Package: podman Version: 3.0.1+dfsg1-2+b2 Severity: important Tags: patch upstream X-Debbugs-Cc: alexan...@alphamar.org Running podman containers rootless seems I was unable to access any network services in a container. The apps work inside the container, but not from the host system. Searching around I found https://github.com/containers/podman/issues/9532 which seems to be the isse I run into. The bug log also mentiones a missing patch in 3.0.1. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US: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 ii containernetworking-plugins 0.9.0-1+b5 ii crun 0.17+dfsg-1 ii golang-github-containers-common 0.33.4+ds1-1 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc62.31-12 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.14.0-1+b2 ii libseccomp2 2.5.1-1 Versions of packages podman recommends: ii buildah 1.19.6+dfsg1-1+b4 ii catatonit 0.1.5-2 ii fuse-overlayfs1.4.0-1 ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b6 ii slirp4netns 1.0.1-2 ii uidmap1:4.8.1-1 Versions of packages podman suggests: pn containers-storage pn docker-compose -- no debconf information
Bug#989803: podman 3.0.1 rootless network issues: Connection reset by peer
Package: podman Version: 3.0.1+dfsg1-2+b2 Severity: important Tags: patch upstream X-Debbugs-Cc: alexan...@alphamar.org Running podman containers rootless seems I was unable to access any network services in a container. The apps work inside the container, but not from the host system. Searching around I found https://github.com/containers/podman/issues/9532 which seems to be the isse I run into. The bug log also mentiones a missing patch in 3.0.1. -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US: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 ii containernetworking-plugins 0.9.0-1+b5 ii crun 0.17+dfsg-1 ii golang-github-containers-common 0.33.4+ds1-1 ii init-system-helpers 1.60 ii iptables 1.8.7-1 ii libc62.31-12 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgpgme11 1.14.0-1+b2 ii libseccomp2 2.5.1-1 Versions of packages podman recommends: ii buildah 1.19.6+dfsg1-1+b4 ii catatonit 0.1.5-2 ii fuse-overlayfs1.4.0-1 ii golang-github-containernetworking-plugin-dnsname 1.1.1+ds1-4+b6 ii slirp4netns 1.0.1-2 ii uidmap1:4.8.1-1 Versions of packages podman suggests: pn containers-storage pn docker-compose -- no debconf information
