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 1518519 - [DOCKER] Builds fail with "error: build error: devmapper: Error mounting"
Summary: [DOCKER] Builds fail with "error: build error: devmapper: Error mounting"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Antonio Murdaca
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
: 1535694 (view as bug list)
Depends On:
Blocks: 1186913
TreeView+ depends on / blocked
 
Reported: 2017-11-29 06:47 UTC by Jaspreet Kaur
Modified: 2021-09-09 12:52 UTC (History)
23 users (show)

Fixed In Version: docker-1.12.6-71.git3e8e77d.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-01-25 12:57:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0202 0 normal SHIPPED_LIVE docker bug fix and enhancement update 2018-01-25 17:25:15 UTC

Description Jaspreet Kaur 2017-11-29 06:47:36 UTC
Description of problem: Builds are failing with below error :

error: build error: devmapper: Error mounting '/dev/mapper/docker-253:7-786433-66102a8b70b2778aac36aa9ef99d6cbb7d9b9f46188ff870807c017496162a7c' on '/var/lib/docker/devicemapper/mnt/66102a8b70b2778aac36aa9ef99d6cbb7d9b9f46188ff870807c017496162a7c': invalid argument


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
 
Actual results: Fails each time with the error


Expected results: It should suceed


Additional info :

Seems similar to  https://github.com/openshift/origin/issues/17330

Comment 2 Cynthia 2017-11-29 18:26:52 UTC
This impacts our user community, can you please priortize this

Comment 7 Cynthia 2017-12-01 18:12:05 UTC
Any updates on this issue 

Thanks,
Cynthia

Comment 8 Vivek Goyal 2017-12-01 18:22:29 UTC
I can't find error message in the log. Where did you get this error message. I will need all the surrounding messages around that and see if something is odd.

Also please provide me a system where problem is reproducible.

Comment 32 Daniel Walsh 2017-12-12 14:02:58 UTC
I believe this would only happen if the container was created on a docker enabled selinux system which was later disabled, on the host.

Comment 33 Daniel Walsh 2017-12-12 14:03:23 UTC
I actually think the system has SELinux disabled.

Comment 34 Daniel Walsh 2017-12-12 14:05:27 UTC
This label also looks strange since it only uses one category.  Not sure if OpenShift allows users to specify the MCS Label?  Using one category is not a great idea,  Since all containers with s0:c12,c* can write to this label.

Comment 54 Daniel Walsh 2018-01-04 19:55:53 UTC
Antonio do we have these patches merged?

Comment 64 Vivek Goyal 2018-01-18 13:23:15 UTC
*** Bug 1535694 has been marked as a duplicate of this bug. ***

Comment 66 errata-xmlrpc 2018-01-25 12:57:49 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.

https://access.redhat.com/errata/RHBA-2018:0202


Note You need to log in before you can comment on or make changes to this bug.