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.
+++ This bug was initially created as a clone of Bug #1371512 +++
Description of problem:
I tried to build a Docker image with a Dockerfile that uses makepkg, from ArchLinux.
SELinux is preventing makepkg from 'send' accesses on the message Unknown.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that makepkg should be allowed send access on the Unknown msg by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'makepkg' --raw | audit2allow -M my-makepkg
# semodule -X 300 -i my-makepkg.pp
Additional Information:
Source Context system_u:system_r:svirt_lxc_net_t:s0:c31,c241
Target Context system_u:object_r:svirt_lxc_net_t:s0:c31,c241
Target Objects Unknown [ msg ]
Source makepkg
Source Path makepkg
Port <Unknown>
Host (removed)
Source RPM Packages
Target RPM Packages
Policy RPM selinux-policy-3.13.1-158.21.fc23.noarch
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name (removed)
Platform Linux (removed) 4.6.6-200.fc23.x86_64 #1 SMP Wed
Aug 10 23:13:35 UTC 2016 x86_64 x86_64
Alert Count 1
First Seen 2016-08-30 13:09:45 CEST
Last Seen 2016-08-30 13:09:45 CEST
Local ID 35eb2690-7ca9-4a0d-9743-491a709f2a82
Raw Audit Messages
type=AVC msg=audit(1472555385.413:2113): avc: denied { send } for pid=40553 comm="makepkg" key=1722255375 scontext=system_u:system_r:svirt_lxc_net_t:s0:c31,c241 tcontext=system_u:object_r:svirt_lxc_net_t:s0:c31,c241 tclass=msg permissive=0
Hash: makepkg,svirt_lxc_net_t,svirt_lxc_net_t,msg,send
Version-Release number of selected component:
selinux-policy-3.13.1-158.21.fc23.noarch
Additional info:
reporter: libreport-2.6.4
hashmarkername: setroubleshoot
kernel: 4.6.6-200.fc23.x86_64
type: libreport
--- Additional comment from Laurent Rineau on 2016-08-30 07:48:04 EDT ---
The end of logs of the build attempt was:
==> Entering fakeroot environment...
libfakeroot, when sending message: Permission denied
--- Additional comment from Daniel Walsh on 2016-08-30 15:46:03 EDT ---
https://github.com/fedora-selinux/selinux-policy/pull/151
We need to get this fix into all Fedora and RHEL7 packages.
--- Additional comment from Daniel Walsh on 2016-08-30 15:47:55 EDT ---
Laurent add this permissions by hand for now using audit2allow.
grep msg /var/log/audit/audit.log | audit2allow -M mymsg
semodule -i mymsg.pp
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/RHBA-2016-2283.html