-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix rootless networking with userns and ports #12227
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -290,7 +290,7 @@ func (c *Container) handleRestartPolicy(ctx context.Context) (_ bool, retErr err | |||
|
|||
// setup slirp4netns again because slirp4netns will die when conmon exits | |||
if c.config.NetMode.IsSlirp4netns() { | |||
err := c.runtime.setupSlirp4netns(c) | |||
err := c.runtime.setupSlirp4netns(c, c.state.NetNS) | |||
if err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason 293 and 294 are separate lines?
LGTM overall |
looks like some test unhappiness @Luap99 |
A rootless container created with a custom userns and forwarded ports did not work. I refactored the network setup to make the setup logic more clear. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
/lgtm |
What this PR does / why we need it:
A rootless container created with a custom userns and forwarded ports
did not work. I refactored the network setup to make the setup logic
more clear.
How to verify it
podman run -it --rm --userns keep-id --network bridge -p 8080:8080 alpine nc -l -p 8080
echo test | nc 127.0.0.1 8080
Which issue(s) this PR fixes:
Special notes for your reviewer: