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

rootless netns, one netns per libpod tmp dir #12348

Merged
merged 1 commit into from
Nov 18, 2021

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Nov 18, 2021

What this PR does / why we need it:

The netns cleanup code is checking if there are running containers, this
can fail if you run several libpod instances with diffrent root/runroot.
To fix it we use one netns for each libpod instances. To prevent name
conflicts we use a hash from the static dir as part of the name.

Previously this worked because we would use the CNI files to check if
the netns was still in use. but this is no longer possible with netavark.

How to verify it

No more rootless netns flakes in CI!

Which issue(s) this PR fixes:

Fixes #12306

Special notes for your reviewer:

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 18, 2021
@mheon
Copy link
Member

mheon commented Nov 18, 2021

Sure, LGTM

The netns cleanup code is checking if there are running containers, this
can fail if you run several libpod instances with diffrent root/runroot.
To fix it we use one netns for each libpod instances. To prevent name
conflicts we use a hash from the static dir as part of the name.

Previously this worked because we would use the CNI files to check if
the netns was still in use. but this is no longer possible with netavark.

[NO NEW TESTS NEEDED]

Fixes containers#12306

Signed-off-by: Paul Holzinger <[email protected]>
@Luap99
Copy link
Member Author

Luap99 commented Nov 18, 2021

search test are failing, we are getting couldn't search registry "registry.redhat.io": pinging container registry registry.redhat.io: invalid status code from registry 503 (Service Unavailable)

@TomSweeneyRedHat
Copy link
Member

LGTM
but you'll need the no new tests needed flag here too.

@Luap99
Copy link
Member Author

Luap99 commented Nov 18, 2021

LGTM but you'll need the no new tests needed flag here too.

The test failures are flakes.

@Luap99
Copy link
Member Author

Luap99 commented Nov 18, 2021

Tests are green

@rhatdan
Copy link
Member

rhatdan commented Nov 18, 2021

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, rhatdan

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-merge-robot openshift-merge-robot merged commit 348aafe into containers:main Nov 18, 2021
@Luap99 Luap99 deleted the rootless-netns branch November 18, 2021 21:00
@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 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 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.

CNI: failed to set bridge addr: "cni-podman1" already has an IP address different from 10.25.31.1/24
5 participants