-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Add "--selinux-enabled" flag for Docker #9334
Conversation
I also set the default log level to "info" as it was already in docs. It is not very verbose, but should help us track various issues easier in testing. kops/pkg/apis/kops/dockerconfig.go Lines 53 to 54 in ba1d87e
|
Just to confirm, is SELinux installed and enabled in your Ubuntu box? It's not installed by default in Ubuntu, and apparently the package migh be broken: https://wiki.ubuntu.com/SELinux The
|
Apparently this message was returned because it failed this check: Which leads to this code, that verifies that SELinux was not enabled on the host (it looks for |
The point of the message was to show that the flag is applied. A bit harder to enable SELinux on Ubuntu, I guess. |
Doesn't seem to work to well on a CentOS 7 box either:
|
/hold |
Tracked down the previous error to an incompatibility between Docker and containerd and will be fixed in a separate PR. |
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.
Thank you @hakman!
I'm not familiar with the code base, but I reviewed the changes and they LGTM.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman, rifelpet 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 |
@bertinatto you should update the test to use this flag instead. |
https://success.docker.com/article/how-to-set-selinux-file-contexts-when-using-a-custom-docker-data-root
I don't thin the current solution does what is expected based on the Docker docs: https://docs.docker.com/engine/reference/commandline/dockerd/#docker-runtime-execution-options
This PR should work better for the desired use case. On my ubuntu box I see this message:
Ref: kubernetes/test-infra#17902
/cc @bertinatto @rifelpet