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.

Bug 1347360

Summary: atomic scanner doesn't work with SELinux enforcing mode
Product: Red Hat Enterprise Linux 7 Reporter: Alex Jia <ajia>
Component: dockerAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DEFERRED QA Contact: atomic-bugs <atomic-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: bbaude, dwalsh, imcleod, jhonce, lsm5, lvrabec, mgrepl, miabbott, mmalik, mpreisle, plautrba, pvrabec, ssekidde, walters
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: docker-1.10.3-43.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-02 09:31:36 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:
Embargoed:
Attachments:
Description Flags
avc none

Comment 1 Brent Baude 2016-06-16 16:19:20 UTC 
I'm on PTO this week but will try to carve out some time to look at it.  

@Martin, is the error "WARNING:Can't import the 'docker' package. Container scanning functionality will be disabled." meaningful at all here?
Comment 2 Daniel Walsh 2016-06-16 16:20:49 UTC 
Alex what AVC's are you seeing?
Comment 3 Alex Jia 2016-06-16 16:45:38 UTC 
Created attachment 1168794 [details]
avc
Comment 4 Alex Jia 2016-06-16 16:46:16 UTC 
(In reply to Daniel Walsh from comment #2)
> Alex what AVC's are you seeing?

Daniel, please check attachments.
Comment 7 Daniel Walsh 2016-06-16 19:53:18 UTC 
The problem seems to be SELinux fighting with overlayfs which we don't support.

The labeling seems to be all screwed up.
Comment 8 Ian McLeod 2016-06-16 19:58:36 UTC 
(In reply to Daniel Walsh from comment #7)
> The problem seems to be SELinux fighting with overlayfs which we don't
> support.
> 
> The labeling seems to be all screwed up.

Could this be related to the SELinux issue we saw with the latest base image build?  (Which is itself related to SELinux xattrs being present in the base image layer tarball.)
Comment 9 Lokesh Mandvekar 2016-06-16 20:43:53 UTC 
with the latest atomic host image atomic scan seems to work well aside from the devmapper messages

$ sudo atomic scan rhel7
docker run -it --rm -v /etc/localtime:/etc/localtime -v /run/atomic/2016-06-16-20-40-00-772810:/scanin -v /var/lib/atomic/openscap/2016-06-16-20-40-00-772810:/scanout:rw,Z -v /etc/oscapd:/etc/oscapd:ro rhel7/openscap oscapd-evaluate scan --no-standard-compliance --targets chroots-in-dir:///scanin --output /scanout
Error deleting container: Error response from daemon: Driver devicemapper failed to remove root filesystem 1916803ba929c36d3349879108492865e604bd1e9fb3097507570ef525b8e314: Device is Busy

rhel7 (sha256:bf203442)

The following issues were found:

     RHSA-2016:1025: pcre security update (Important)
     Severity: Important
       RHSA URL: https://rhn.redhat.com/errata/RHSA-2016-1025.html
       RHSA ID: RHSA-2016:1025-00
       Associated CVEs:
           CVE ID: CVE-2015-2328
           CVE URL: https://access.redhat.com/security/cve/CVE-2015-2328
           CVE ID: CVE-2015-3217
           CVE URL: https://access.redhat.com/security/cve/CVE-2015-3217
           CVE ID: CVE-2015-5073
           CVE URL: https://access.redhat.com/security/cve/CVE-2015-5073
           CVE ID: CVE-2015-8385
           CVE URL: https://access.redhat.com/security/cve/CVE-2015-8385
           CVE ID: CVE-2015-8386
           CVE URL: https://access.redhat.com/security/cve/CVE-2015-8386
           CVE ID: CVE-2015-8388
           CVE URL: https://access.redhat.com/security/cve/CVE-2015-8388
           CVE ID: CVE-2015-8391
           CVE URL: https://access.redhat.com/security/cve/CVE-2015-8391
           CVE ID: CVE-2016-3191
           CVE URL: https://access.redhat.com/security/cve/CVE-2016-3191


Files associated with this scan are in /var/lib/atomic/openscap/2016-06-16-20-40-00-772810.
Comment 10 Lokesh Mandvekar 2016-06-16 20:45:59 UTC 
the 'ostree admin unlock' step before manually installing additional rpms apparently caused selinux-overlayfs issues like Dan pointed earlier
Comment 11 Alex Jia 2016-06-17 01:33:53 UTC 
(In reply to Daniel Walsh from comment #7)
> The problem seems to be SELinux fighting with overlayfs which we don't
> support.
> 
> The labeling seems to be all screwed up.

It should be the root reason, but if someone wanna hack Atomic Host w/ development or hotfix mode, it's possible to encounter similar issue, we should document this at least.
Comment 12 Martin Preisler 2016-06-17 15:25:30 UTC 
(In reply to Brent Baude from comment #1)
> I'm on PTO this week but will try to carve out some time to look at it.  
> 
> @Martin, is the error "WARNING:Can't import the 'docker' package. Container
> scanning functionality will be disabled." meaningful at all here?

This warning can be safely ignored.