-
Notifications
You must be signed in to change notification settings - Fork 92
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
docker run with container-selinux-2.77-1.el7_6.noarch does not work #63
Comments
ping @rhatdan ptal 🤗 |
This looks like the docker daemon or containerd is mislabeled. It is not because of container selinux yum -y update container-selinux systemctl restart docker ps -eZ | grep docker Should be running as container_runtime_t |
Thanks, merged it. Will need to back port those changes into the branch that works on RHEL7. |
@rhatdan do you know if the patch has been back ported to the correct RHEL7 branch? (which branch should it be back ported to? happy to open a backport PR) |
Should be in container-selinux-2.94. @lsm5 Did this make the cut yesterday? |
2.94 ship date is about 3 weeks from now, so let's keep this open until then. |
Thanks! |
Looks like
|
I'm still able to exactly reproduce the error with |
@andrewhsu Could you show me the AVCs you are seeing? Could you verify if docker and containerd are running as container_runtime_t? |
@rhatdan apologies for the delayed reply... With CentOS7:
However, I noticed RHEL7 has a newer
When will |
No idea on CentOS, usually they grab the latest available packages. |
@andrewhsu |
On a rhel7 system with
container-selinux-2.77-1.el7_6.noarch
:The corresponding
denied
message in selinux log file/var/log/audit/audit.log
is:Is it perhaps related to this change? 99e2cfd...5133af6
I'm able to workaround the problem on rhel7 for now by downgrading:
Btw, this "permission denied" problem does not exist on centos7, I believe because container-selinux only goes up to version 2.74
The text was updated successfully, but these errors were encountered: