Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The problem is the docker-selinux package did not install properly. There are build differences between 7.3 and 7.2.7 selinux-policy package that is causing docker-selinux to blow up.
I agree this is a blocker.
The latest docker-selinux should have /usr/bin/docker* labeled as docker_exec_t.
yum reinstall docker-selinux
restorecon -v /usr/bin/docker*
ls -lZ /usr/bin/docker*
If they are all labeled docker_exec_t, then you should be able to
systemctl restart docker Or docker-latest
Now check the label on the docker process.
ps -eZ | grep docker
They should all be labeled docker_t.
Yes I just checked in a fix for this in docker-selinux.
edbbfc9001fbf949e4fb98392c647cdd820f06fe fixes this issue.
Seems selinux policy in RHEL now has a domain for k8s which defines this path.
This policy is not present in Rawhide though.
VERIFIED with these versions:
docker-1.10.3-53.el7.x86_64
docker-selinux-1.10.3-53.el7.x86_64
selinux-policy-3.13.1-98.el7.noarch
Beaker job which works with atomic/docker executables:
https://beaker.engineering.redhat.com/recipes/3085819#tasks
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-2634.html