-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Revert Patch to relabel if selinux not enabled #10253
Conversation
@dustymabe PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@rhatdan - we may want to consider keeping the tests and adjusting them to the correct behavior (now that we know what that is). |
@tunacado Could you point me back to the original issue that caused us to change the labeling practice. I might have to add a containers.conf option to give you what you want. |
Fixes: #10209 |
48c9645
to
88421fb
Compare
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 <dwalsh@redhat.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dustymabe, giuseppe, 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 |
@rhatdan good to merge? /lgtm |
Yes we can merge. But I need feedback from @tunacado about the next step. |
Revert : #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 dwalsh@redhat.com