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

Don't relabel volumes if running in a privileged container #9895

Merged
merged 1 commit into from
Apr 5, 2021

Conversation

rhatdan
Copy link
Member

@rhatdan rhatdan commented Mar 30, 2021

Docker does not relabel this content, and openstack is running
containers in this manner. There is a penalty for doing this
on each container, that is not worth taking on a disable SELinux
container.

Signed-off-by: Daniel J Walsh [email protected]

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 30, 2021
@rhatdan
Copy link
Member Author

rhatdan commented Mar 30, 2021

@tunacado PTAL

return nil, err
}
} else {
logrus.Infof("Ignoring label request on volumes for label disabled containers %q", m.Source)
Copy link
Member

Choose a reason for hiding this comment

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

Suggest reword to "Not relabeling volume %q in container %s as SELinux is disabled", m.Source, c.ID()

@TomSweeneyRedHat
Copy link
Member

LGTM once @mheon's comment is addressed.

@robbmanes
Copy link
Contributor

LGTM

@TomSweeneyRedHat
Copy link
Member

@rhatdan unhappy red tests.

Docker does not relabel this content, and openstack is running
containers in this manner.  There is a penalty for doing this
on each container, that is not worth taking on a disable SELinux
container.

Signed-off-by: Daniel J Walsh <[email protected]>
@rhatdan rhatdan added the lgtm Indicates that a PR is ready to be merged. label Apr 5, 2021
@openshift-merge-robot openshift-merge-robot merged commit ca095e4 into containers:master Apr 5, 2021
@rhatdan
Copy link
Member Author

rhatdan commented May 6, 2021

@tunacado @dustymabe Has pointed out that this breaks compatibility with Docker, so I need to revert this PR.

rhatdan added a commit to rhatdan/podman that referenced this pull request May 6, 2021
Revert : containers#9895

Turns out that if Docker is in --selinux-enabeled, it still relabels if
the user tells the system to, even if running a --privileged container
or if the selinux separation is disabled --security-opt label=disable.

Signed-off-by: Daniel J Walsh <[email protected]>
@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 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 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.

6 participants