Bug 1386916

Summary: remove docker.pp from selinux-policy and replace with container.pp
Product: Red Hat Enterprise Linux 7 Reporter: Daniel Walsh <dwalsh>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: unspecified Docs Contact: Mirek Jahoda <mjahoda>
Priority: unspecified    
Version: 7.3CC: dominick.grift, dwalsh, extras-qa, lvrabec, mgrepl, mmalik, pasik, plautrba, pmoore, pvrabec, ssekidde
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: selinux-policy-3.13.1-121.el7 Doc Type: Bug Fix
Doc Text:
`docker.pp` replaced with `container.pp` in _selinux-policy_ Prior to this update, the `container.te` file in the _container-selinux_ package contained Docker interfaces, which point to the equivalent container interfaces, and also the `docker.if` file. Consequently, when compiling the `container.te` file, the compiler warned about duplicate interfaces. With this update, the `docker.pp` file in the _selinux-policy_ package has been replaced with the `container.pp` file, and the warning no longer occurs in the described scenario.
Story Points: ---
Clone Of: 1386912 Environment:
Last Closed: 2017-08-01 15:17:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1386912    
Bug Blocks: 1377248    

Description Daniel Walsh 2016-10-19 19:50:16 UTC
+++ This bug was initially created as a clone of Bug #1386912 +++

container.te in container-selinux now includes docker Interfaces which point to the equivalent container* interfaces.

Since we still have docker.if shipping, when you compile container.te the compiler warns about duplicate interfaces.

--- Additional comment from Daniel Walsh on 2016-10-19 15:40:17 EDT ---

This will need to be fixed in Fedora25 and 25 as well as rhel7.

Comment 6 errata-xmlrpc 2017-08-01 15:17:42 UTC
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.