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.
Description of problem:
It looks like we are encountering this since upgrading to RHEL 7.3. On my personal boxes, as well as our automation testing framework for Satellite 6, we are blocked by what appears to be this bug. If selinux is disabled, then containers run properly.
[root@rhsm-qe-1 content-host-d]# docker run hello-world
permission denied
docker: Error response from daemon: Container command could not be invoked..
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 7.3 (Maipo)
How reproducible:
Always
Steps to Reproduce:
1. Ensure selinux is enabled.
2. Attempt to run a container
Actual results:
[root@rhsm-qe-1 content-host-d]# docker run hello-world
permission denied
docker: Error response from daemon: Container command could not be invoked..
Expected results:
The container runs properly, without disabling selinux
Additional info:
It looks like this bug, which was closed, may be the same issue. https://bugzilla.redhat.com/show_bug.cgi?id=1327740
There seems to be a mismatch in the docker-selinux package. I am not sure if the right version was shipped.
Simple fix is to do
chcon -t docker_exec_t /usr/bin/docker*
systemctl restart docker
And everything should work.
That was indeed a simple fix! How soon can we get the proper version in?
fyi
[root@rhsm-qe-1 content-host-d]# rpm -qa | grep docker
docker-selinux-1.10.3-46.el7.14.x86_64
python-pulp-docker-common-2.0.3-1.el7sat.noarch
docker-rhel-push-plugin-1.10.3-46.el7.14.x86_64
docker-1.10.3-46.el7.14.x86_64
tfm-rubygem-hammer_cli_foreman_docker-0.0.6-1.el7sat.noarch
docker-common-1.10.3-46.el7.14.x86_64
tfm-rubygem-docker-api-1.28.0-1.el7sat.noarch
pulp-docker-plugins-2.0.3-1.el7sat.noarch
tfm-rubygem-foreman_docker-2.0.1.11-1.el7sat.noarch