Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionStephen Benjamin
2016-03-24 18:48:03 UTC
Description of problem:
Creating a new compute resource suggests to use the socket (e.g. if docker's running locally) but this is not allowed by selinux
Version-Release number of selected component (if applicable):
6.2 SNAP 5.1
How reproducible:
Always
Steps to Reproduce:
1. Create docker compute resource with URL unix:///var/run/docker.sock
2. Click test connection
Actual results:
type=AVC msg=audit(1458845053.734:13120): avc: denied { connectto } for pid=23694 comm="diagnostic_con*" path="/run/docker.sock" scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:system_r:docker_t:s0 tclass=unix_stream_socket
Expected results:
Works
Additional info:
The boolean is on:
[root@sat-r220-06 ~]# getsebool -a | grep docker
docker_connect_any --> off
passenger_can_connect_docker_tcp --> on
passenger_can_connect_docker_unix --> on
Description of problem: Creating a new compute resource suggests to use the socket (e.g. if docker's running locally) but this is not allowed by selinux Version-Release number of selected component (if applicable): 6.2 SNAP 5.1 How reproducible: Always Steps to Reproduce: 1. Create docker compute resource with URL unix:///var/run/docker.sock 2. Click test connection Actual results: type=AVC msg=audit(1458845053.734:13120): avc: denied { connectto } for pid=23694 comm="diagnostic_con*" path="/run/docker.sock" scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:system_r:docker_t:s0 tclass=unix_stream_socket Expected results: Works Additional info: The boolean is on: [root@sat-r220-06 ~]# getsebool -a | grep docker docker_connect_any --> off passenger_can_connect_docker_tcp --> on passenger_can_connect_docker_unix --> on