Cloudera Community

Support Questions

Find answers, ask questions, and share your expertise
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Solved Go to solution

Unable to install/start docker.

avatar
author-rank das_dineshk
Expert Contributor

Created ‎04-03-2017 01:21 PM

Unable to install dockeer-engine, getting below error.

Docker is not working after yum install and yum upgrade.

I did following to completely unistall docker and after that tried for a fresh installation but its throwing below errors.

1> yum remove docker

2> rm -rf /etc/yum.repos.d/docker.repo

3> rm -rf /var/lib/docker*

4> rm -rf /var/cache/yum/x86_64/7Server/docker*

10-74-58-106:/root # yum install docker-engine
Loaded plugins: langpacks, product-id, rhnplugin, search-disabled-repos
This system is receiving updates from RHN Classic or Red Hat Satellite.
Resolving Dependencies
--> Running transaction check
---> Package docker-engine.x86_64 0:17.03.1.ce-1.el7.centos will be installed
--> Processing Dependency: docker-engine-selinux >= 17.03.1.ce-1.el7.centos for package: docker-engine-17.03.1.ce-1.el7.centos.x86_64
--> Running transaction check
---> Package docker-engine-selinux.noarch 0:17.03.1.ce-1.el7.centos will be installed
--> Processing Dependency: selinux-policy-base >= 3.13.1-102 for package: docker-engine-selinux-17.03.1.ce-1.el7.centos.noarch
--> Processing Dependency: selinux-policy-targeted >= 3.13.1-102 for package: docker-engine-selinux-17.03.1.ce-1.el7.centos.noarch
--> Processing Conflict: docker-engine-selinux-17.03.1.ce-1.el7.centos.noarch conflicts docker-selinux
--> Finished Dependency Resolution
Error: Package: docker-engine-selinux-17.03.1.ce-1.el7.centos.noarch (dockerrepo)
           Requires: selinux-policy-base >= 3.13.1-102
           Installed: selinux-policy-targeted-3.13.1-60.el7_2.7.noarch (@rhel7-x86_64-2016-07)
               selinux-policy-base = 3.13.1-60.el7_2.7
           Available: selinux-policy-minimum-3.12.1-153.el7.noarch (rhel7-x86_64-2016-07)
               selinux-policy-base = 3.12.1-153.el7
           Available: selinux-policy-minimum-3.12.1-153.el7_0.10.noarch (rhel7-x86_64-2016-07)
               selinux-policy-base = 3.12.1-153.el7_0.10
           Available: selinux-policy-minimum-3.12.1-153.el7_0.11.noarch (rhel7-x86_64-2016-07)
               selinux-policy-base = 3.12.1-153.el7_0.11
           Available: selinux-policy-minimum-3.12.1-153.el7_0.12.noarch (rhel7-x86_64-2016-07)
               selinux-policy-base = 3.12.1-153.el7_0.12
           Available: selinux-policy-minimum-3.12.1-153.el7_0.13.noarch (rhel7-x86_64-2016-07)
               selinux-policy-base = 3.12.1-153.el7_0.13
           Available: selinux-policy-minimum-3.13.1-23.el7.noarch (rhel7-x86_64-2016-07)

Error: Package: docker-engine-selinux-17.03.1.ce-1.el7.centos.noarch (dockerrepo)
           Requires: selinux-policy-targeted >= 3.13.1-102
           Installed: selinux-policy-targeted-3.13.1-60.el7_2.7.noarch (@rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-60.el7_2.7
           Available: selinux-policy-targeted-3.12.1-153.el7.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.12.1-153.el7
           Available: selinux-policy-targeted-3.12.1-153.el7_0.10.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.12.1-153.el7_0.10
           Available: selinux-policy-targeted-3.12.1-153.el7_0.11.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.12.1-153.el7_0.11
           Available: selinux-policy-targeted-3.12.1-153.el7_0.12.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.12.1-153.el7_0.12
           Available: selinux-policy-targeted-3.12.1-153.el7_0.13.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.12.1-153.el7_0.13
           Available: selinux-policy-targeted-3.13.1-23.el7.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-23.el7
           Available: selinux-policy-targeted-3.13.1-23.el7_1.7.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-23.el7_1.7
           Available: selinux-policy-targeted-3.13.1-23.el7_1.8.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-23.el7_1.8
           Available: selinux-policy-targeted-3.13.1-23.el7_1.13.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-23.el7_1.13
           Available: selinux-policy-targeted-3.13.1-23.el7_1.17.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-23.el7_1.17
           Available: selinux-policy-targeted-3.13.1-23.el7_1.18.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-23.el7_1.18
           Available: selinux-policy-targeted-3.13.1-23.el7_1.21.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-23.el7_1.21
           Available: selinux-policy-targeted-3.13.1-60.el7.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-60.el7
           Available: selinux-policy-targeted-3.13.1-60.el7_2.3.noarch (rhel7-x86_64-2016-07)
               selinux-policy-targeted = 3.13.1-60.el7_2.3
Error: docker-engine-selinux conflicts with docker-selinux-1.10.3-44.el7.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

while starting docker also am facing issues 

ip-10-74-58-106:/root # systemctl start docker
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.

Can someone please help me here. If possible please share me the link to download dockerized version of latest HDP.

5,906 Views
0 Kudos
1 ACCEPTED SOLUTION

avatar
author-rank das_dineshk
Expert Contributor

Created ‎04-04-2017 03:01 PM

I got the fix. This was all because of docker version mismatching with selinux. I tried to install lesser version of docker and it worked for me 

  yum -y install docker-engine-1.12.6-1.el7.centos docker-engine-selinux-1.12.6-1.el7.centos

View solution in original post

3,873 Views
4 REPLIES 4

avatar
author-rank zzseli
New Contributor

Created ‎04-03-2017 02:20 PM

If you run systemctl status docker.service you will get the logs and it might be more clear what the problem is.

So could you please post the full message output from systemctl status docker.service and journalctl -xe as i need more detail to help you out.

3,873 Views
0 Kudos

avatar
author-rank das_dineshk
Expert Contributor

Created ‎04-04-2017 08:10 AM 

# journalctl -xe
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished starting up.
--
-- The start-up result is done.
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com systemd[1]: Starting user-0.slice.
-- Subject: Unit user-0.slice has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has begun starting up.
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com systemd[1]: Started Session 31 of user root.
-- Subject: Unit session-31.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-31.scope has finished starting up.
--
-- The start-up result is done.
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com systemd[1]: Starting Session 31 of user root.
-- Subject: Unit session-31.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-31.scope has begun starting up.
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com CROND[4903]: (root) CMD (run-parts /etc/cron.hourly)
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com run-parts(/etc/cron.hourly)[4906]: starting 0anacron
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com run-parts(/etc/cron.hourly)[4912]: finished 0anacron
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com run-parts(/etc/cron.hourly)[4914]: starting 0yum-hourly.cron
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com run-parts(/etc/cron.hourly)[4918]: finished 0yum-hourly.cron
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com systemd[1]: Removed slice user-0.slice.
-- Subject: Unit user-0.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished shutting down.
Apr 03 10:01:01 ip-10-74-58-106.ebiz.verizon.com systemd[1]: Stopping user-0.slice.
-- Subject: Unit user-0.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has begun shutting down.
lines 3227-3269/3269 (END)
3,873 Views
0 Kudos

avatar
author-rank orendain
Guru

Created ‎04-03-2017 09:18 PM

@Dinesh Das

You'll have to uninstall old versions of Docker first. The logs you posted show docker-selinux may currently be installed. Try this:

sudo yum remove docker \
                  docker-common \
                  container-selinux \
                  docker-selinux \
                  docker-engine
3,873 Views
0 Kudos

avatar
author-rank das_dineshk
Expert Contributor

Created ‎04-04-2017 03:01 PM

I got the fix. This was all because of docker version mismatching with selinux. I tried to install lesser version of docker and it worked for me 

  yum -y install docker-engine-1.12.6-1.el7.centos docker-engine-selinux-1.12.6-1.el7.centos
3,874 Views
Announcements
What's New @ Cloudera
[RELEASED] Cloudera Streaming Analytics 1.14 for Cloudera Pu...
What's New @ Cloudera
Cloudera Data Engineering 1.23: Access Spark from Your Favor...
What's New @ Cloudera
HBase REST server scaling support is Generally Available
What's New @ Cloudera
New CLI option in the update-database command
What's New @ Cloudera
New Action menu item in the Cloudera Operational Database UI
View More Announcements