rootless: podman run --net=<CNI> -p <PORT> is broken on master
#9065
Labels
CNI
Bug with CNI networking for root containers
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
rootless
Comments
openshift-ci-robot
added
the
kind/bug
|
@giuseppe @AkihiroSuda Could one of you open a PR to fix |
|
PR here: #9066 |
giuseppe
added a commit
to giuseppe/libpod
that referenced
this issue
Jan 23, 2021
if a CNI network is added to the container, use the IP address in that network instead of hard-coding the slirp4netns default. commit 5e65f0b introduced this regression. Closes: containers#9065 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
iwita
pushed a commit
to iwita/podman
that referenced
this issue
Jan 26, 2021
if a CNI network is added to the container, use the IP address in that network instead of hard-coding the slirp4netns default. commit 5e65f0b introduced this regression. Closes: containers#9065 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman run --net=<CNI> -p <PORT>with rootless is broken on master, due to regression in #9052Steps to reproduce the issue:
podman network create foopodman run -d --name nginx --network foo -p 8080:80 nginx:alpinecurl localhost:8080Describe the results you received:
curl: (56) Recv failure: Connection reset by peerDescribe the results you expected:
...<title>Welcome to nginx!</title>...Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:f02aba6 is broken.
6fd83de works.
regression in #9052
The text was updated successfully, but these errors were encountered: