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

oci_conmon: not make accessible dirs if not needed #4859

Conversation

giuseppe
Copy link
Member

@giuseppe giuseppe commented Jan 14, 2020

do not change the permissions mask for the rundir and the tmpdir when running a container with a user namespace and the current user is mapped inside the user namespace.

The change was introduced with 849548f, that dropped the intermediate mount namespace in favor of allowing root into the user namespace to access these directories.

Closes: #4846

Signed-off-by: Giuseppe Scrivano [email protected]

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

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

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS labels Jan 14, 2020
@rhatdan
Copy link
Member

rhatdan commented Jan 14, 2020

Very cool if this works.
LGTM

@giuseppe giuseppe force-pushed the not-change-permission-for-rundir-tmpdir branch from a2f9a56 to 28a7c73 Compare January 14, 2020 13:42
@giuseppe giuseppe changed the title oci_conmon: not make accessible rundir and tmpdir oci_conmon: not make accessible dirs if not needed Jan 14, 2020
@giuseppe giuseppe force-pushed the not-change-permission-for-rundir-tmpdir branch from 28a7c73 to b38a7cd Compare January 14, 2020 13:45
do not change the permissions mask for the rundir and the tmpdir when
running a container with a user namespace and the current user is
mapped inside the user namespace.

The change was introduced with
849548f, that dropped the
intermediate mount namespace in favor of allowing root into the user
namespace to access these directories.

Closes: containers#4846

Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe giuseppe force-pushed the not-change-permission-for-rundir-tmpdir branch from b38a7cd to 6818504 Compare January 14, 2020 13:45
@giuseppe
Copy link
Member Author

Very cool if this works.
LGTM

so now I remember where it was failing. If the user is not mapped inside of the user namespace, it won't have access to any temporary file we create (such as hostname, .containerenv, passwd) and the OCI runtime will fail.

The correct check is to verify if the current user is mapped inside the user namespace.

@mheon
Copy link
Member

mheon commented Jan 14, 2020

Huh. Neat. LGTM once this goes green.

@rhatdan
Copy link
Member

rhatdan commented Jan 14, 2020

/lgtm
/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 14, 2020
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2020
@rhatdan
Copy link
Member

rhatdan commented Jan 15, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 15, 2020
@openshift-merge-robot openshift-merge-robot merged commit d914cc2 into containers:master Jan 15, 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.

unexpected permission change of /run/user/$UID
5 participants