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

libpod: allow userns=keep-id for root #17350

Merged

Conversation

giuseppe
Copy link
Member

@giuseppe giuseppe commented Feb 3, 2023

copy the current mapping into a new user namespace, and run into a separate user namespace.

Closes: #17337

Signed-off-by: Giuseppe Scrivano gscrivan@redhat.com

Does this PR introduce a user-facing change?

Now --userns=keep-id also works for root containers and it copies the current mapping into a new user namespace

@openshift-ci openshift-ci bot added release-note approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 3, 2023
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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flouthoc, giuseppe

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

@Luap99
Copy link
Member

Luap99 commented Feb 3, 2023

Is there an actual difference between running in a userns with the same mappings compared to just running in the host ns?

@giuseppe
Copy link
Member Author

giuseppe commented Feb 3, 2023

Is there an actual difference between running in a userns with the same mappings compared to just running in the host ns?

only minor differences compared to using a mapping where the "real" root is not mapped.

There are few places in the kernel that just check if it is running in the initial user namespace.

copy the current mapping into a new user namespace, and run into a
separate user namespace.

Closes: containers#17337

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

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

/lgtm

I changed your release note because it said --userns=auto instead of keep-id, assuming that this was a typo.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2023
@openshift-merge-robot openshift-merge-robot merged commit 3654a26 into containers:main Feb 3, 2023
@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 12, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 12, 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. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature]: Ignore userns=keep-id in rootful mode, instead of erroring out
4 participants