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 1306100 - RHEL 7.1 docker 1.8.2 missing libdevmapper dependency
Summary: RHEL 7.1 docker 1.8.2 missing libdevmapper dependency
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.1
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
: 1306101 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-10 01:54 UTC by Øystein Bedin
Modified: 2019-03-06 00:39 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-03 20:06:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Øystein Bedin 2016-02-10 01:54:06 UTC 
Description of problem:
When using a RHEL7.1 system to install docker, it fails with a missing libdevmapper dependency. 

Version-Release number of selected component (if applicable):
RHEL: 7.1
Docker: 1.8.2-10
device-mapper-libs: libdevmapper.so.1.02(DM_1_02_97)

How reproducible:
Install a RHEL 7.1 system, lock it to 7.1 using "subscription-manager release" then attempt a "yum install docker".

Steps to Reproduce:
1. Install RHEL 7.1
2. Use "subscription-manager release --set=7.1" to lock it in on 7.1
3. Use "yum install docker" to see the error in dependencies

Actual results:
# yum install docker
Resolving Dependencies
--> Running transaction check
---> Package docker.x86_64 0:1.8.2-10.el7 will be installed
--> Processing Dependency: docker-selinux >= 1.8.2-10.el7 for package: docker-1.8.2-10.el7.x86_64
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit) for package: docker-1.8.2-10.el7.x86_64
--> Running transaction check
---> Package docker.x86_64 0:1.8.2-10.el7 will be installed
--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_97)(64bit) for package: docker-1.8.2-10.el7.x86_64
---> Package docker-selinux.x86_64 0:1.8.2-10.el7 will be installed
--> Finished Dependency Resolution
Error: Package: docker-1.8.2-10.el7.x86_64 (rhel-7-server-extras-rpms)
           Requires: libdevmapper.so.1.02(DM_1_02_97)(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


Expected results:
Docker should install A_OK on RHEL 7.1

Additional info:
Comment 2 Øystein Bedin 2016-02-10 02:07:34 UTC 
*** Bug 1306101 has been marked as a duplicate of this bug. ***
Comment 3 Lokesh Mandvekar 2016-02-10 14:04:36 UTC 
shouldn't it be --set=7.2 ?
Comment 4 Øystein Bedin 2016-02-10 15:59:16 UTC 
(In reply to Lokesh Mandvekar from comment #3)
> shouldn't it be --set=7.2 ?

No, should be 7.1 as outlined above. It works with RHEL 7.2, but for this scenario, we need to be able to continue using RHEL 7.1
Comment 5 Lokesh Mandvekar 2016-02-10 18:13:39 UTC 
Is this gonna be a blocker for 7.2.2 release? or can this wait until 7.2.3?
Comment 6 Micah Abbott 2016-02-10 18:17:46 UTC 
I believe Martin said this can wait until 7.2.3
Comment 7 Lokesh Mandvekar 2016-02-10 18:28:24 UTC 
(In reply to Micah Abbott from comment #6)
> I believe Martin said this can wait until 7.2.3

ah yes, just saw Martin's reply on IRC.

Øystein, I just wanna make sure people aren't blocked entirely until 7.2.3 (scheduled for Mar 29th). My guess is we could provide manual workarounds/support to users to fetch those dependencies and then install docker-1.8.2, correct me if I'm wrong.
Comment 8 Øystein Bedin 2016-02-10 19:13:58 UTC 
(In reply to Lokesh Mandvekar from comment #7)
> (In reply to Micah Abbott from comment #6)
> > I believe Martin said this can wait until 7.2.3
> 
> ah yes, just saw Martin's reply on IRC.
> 
> Øystein, I just wanna make sure people aren't blocked entirely until 7.2.3
> (scheduled for Mar 29th). My guess is we could provide manual
> workarounds/support to users to fetch those dependencies and then install
> docker-1.8.2, correct me if I'm wrong.

I'm not sure about the relationship between 7.2.3 and 7.1 for docker dependencies, but this is an issue with RHEL 7.1 that needs to be addressed. In other words, seems that docker was update but not the dependencies that go with RHEL 7.1. As long as the correct dependencies are made available in some way for 7.1, that would be all that's needed from what I can tell.
Comment 10 Lokesh Mandvekar 2016-02-10 21:48:17 UTC 
(In reply to Øystein Bedin from comment #8)
> 
> I'm not sure about the relationship between 7.2.3 and 7.1 for docker
> dependencies, but this is an issue with RHEL 7.1 that needs to be addressed.
> In other words, seems that docker was update but not the dependencies that
> go with RHEL 7.1. As long as the correct dependencies are made available in
> some way for 7.1, that would be all that's needed from what I can tell.

Looks like device-mapper-libs for 7.1 isn't going to work for the existing docker and this looks like something to be handled on the device-mapper side itself. Do you know if it's possible to upgrade device-mapper itself on 7.1?

A workaround could be enabling some repos to install a device-mapper update and disabling them after the update is done. Would that be ok?
Comment 11 Øystein Bedin 2016-02-10 22:00:35 UTC 
(In reply to Lokesh Mandvekar from comment #10)
> (In reply to Øystein Bedin from comment #8)
> > 
> > I'm not sure about the relationship between 7.2.3 and 7.1 for docker
> > dependencies, but this is an issue with RHEL 7.1 that needs to be addressed.
> > In other words, seems that docker was update but not the dependencies that
> > go with RHEL 7.1. As long as the correct dependencies are made available in
> > some way for 7.1, that would be all that's needed from what I can tell.
> 
> Looks like device-mapper-libs for 7.1 isn't going to work for the existing
> docker and this looks like something to be handled on the device-mapper side
> itself. Do you know if it's possible to upgrade device-mapper itself on 7.1?
> 
> A workaround could be enabling some repos to install a device-mapper update
> and disabling them after the update is done. Would that be ok?

I have looked for an update to device-mapper-libs, but haven't found a repo that has a newer version available for RHEL 7.1. If you can point me to one, that would be great. 

Temporarily enabling a repo for this purpose would be fine as a workaround to get us going, but probably not as a permanent fix for 7.1.
Comment 12 Lokesh Mandvekar 2016-02-11 20:18:23 UTC 
(In reply to Øystein Bedin from comment #11)
> I have looked for an update to device-mapper-libs, but haven't found a repo
> that has a newer version available for RHEL 7.1. If you can point me to one,
> that would be great. 
> 
> Temporarily enabling a repo for this purpose would be fine as a workaround
> to get us going, but probably not as a permanent fix for 7.1.

But if we do this, would that resulting distro still be 7.1? Guess not. Is an upgrade to 7.1.x or 7.2 an absolute no-no for the user? I gotta check if this is something that can be fixed in the docker side or if it's an absolute requirement to update device-mapper.
Comment 17 Subhendu Ghosh 2016-03-31 21:07:54 UTC 
Docker currently has, and  may continue to have dependencies on underlying features that were released after RHEL 7.1. In order to update to a newer version of Docker, all the underlying dependencies must be satisfied. 

In this particular instance there is a requirement to upgrade the device-mapper-libs to a minimum version required by Docker for feature and bug fix support. device-mapper-libs in turn may have other dependencies.

Hence the statement is Docker update must be rpm dependency complete at the very least and certain features of Docker might require installation or upgrade of other elements as well (ex. Docker+overlayfs support requires the RHEL 7.2 kernel as a minimum kernel level).
Comment 18 Lokesh Mandvekar 2016-05-23 18:56:06 UTC 
Can we close this one?
Note You need to log in before you can comment on or make changes to this bug.