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

run: Allow using just one jail per container on FreeBSD #5176

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

dfr
Copy link
Contributor

@dfr dfr commented Nov 17, 2023

In FreeBSD-14.0, it is possible to configure a jail's network settings from outside the jail using ifconfig and route's new '-j' option. This removes the need for a separate jail to own the container's vnet.

This support will also be present in future FreeBSD-13.x releases starting with FreeBSD-13.3.

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This reduces the complexity and cost of running containers on FreeBSD 14

How to verify it

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

@openshift-ci openshift-ci bot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Nov 17, 2023
@rhatdan
Copy link
Member

rhatdan commented Nov 17, 2023

/approve
lgtm

@flouthoc
Copy link
Collaborator

@dfr Could you please rebase. Thanks.

In FreeBSD-14.0, it is possible to configure a jail's network settings
from outside the jail using ifconfig and route's new '-j' option. This
removes the need for a separate jail to own the container's vnet.

This support will also be present in future FreeBSD-13.x releases
starting with FreeBSD-13.3.

[NO NEW TESTS NEEDED]

Signed-off-by: Doug Rabson <dfr@rabson.org>
@dfr
Copy link
Contributor Author

dfr commented Nov 21, 2023

@dfr Could you please rebase. Thanks.

Done

Copy link
Collaborator

@flouthoc flouthoc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve
/hold

Copy link
Contributor

openshift-ci bot commented Nov 21, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dfr, flouthoc, 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

@rhatdan
Copy link
Member

rhatdan commented Nov 21, 2023

/hold cancel

@openshift-merge-bot openshift-merge-bot bot merged commit b9adba5 into containers:main Nov 21, 2023
@dfr dfr deleted the freebsd-vnet branch November 21, 2023 14:23
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm locked - please file new issue/PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants