Skip to content
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

Do not configure CNI when slirp4netns is requested #4853

Merged

Conversation

mheon
Copy link
Member

@mheon mheon commented Jan 13, 2020

Our networking code bakes in a lot of assumptions about how networking should work - that CNI is always used with root, and that slirp4netns is always used only with rootless. These are not safe assumptions. This fixes one particular issue, which would cause CNI to also be run when slirp4netns was requested as root.

Fixes: #4687

Our networking code bakes in a lot of assumptions about how
networking should work - that CNI is *always* used with root, and
that slirp4netns is *always* used only with rootless. These are
not safe assumptions. This fixes one particular issue, which
would cause CNI to also be run when slirp4netns was requested as
root.

Fixes: containers#4687

Signed-off-by: Matthew Heon <[email protected]>
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mheon

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 13, 2020
@AkihiroSuda
Copy link
Collaborator

AkihiroSuda commented Jan 13, 2020

rootlessport needs to be enabled as well, when slirp4netns is used?

Also, what is the usecase of this?

@mheon
Copy link
Member Author

mheon commented Jan 13, 2020

I'm not honestly sure - support for slirp4netns as root was added at some point in the past, but I can't recall why. It doesn't seem to have many users.

@baude
Copy link
Member

baude commented Jan 13, 2020

code LGTM

@rhatdan
Copy link
Member

rhatdan commented Jan 13, 2020

@AkihiroSuda Most likely running podman inside of a container.

@rhatdan
Copy link
Member

rhatdan commented Jan 13, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 13, 2020
@openshift-merge-robot openshift-merge-robot merged commit c1d9366 into containers:master Jan 13, 2020
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Uses/requires CNI for slirp4ns
6 participants