-
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
Don't relabel volumes if running in a privileged container #9895
Conversation
[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 |
@tunacado PTAL |
libpod/container_internal_linux.go
Outdated
return nil, err | ||
} | ||
} else { | ||
logrus.Infof("Ignoring label request on volumes for label disabled containers %q", m.Source) |
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.
Suggest reword to "Not relabeling volume %q in container %s as SELinux is disabled", m.Source, c.ID()
LGTM once @mheon's comment is addressed. |
LGTM |
@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]>
@tunacado @dustymabe Has pointed out that this breaks compatibility with Docker, so I need to revert this PR. |
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]>
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]