Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)

Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.

Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)

Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.

Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional

A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.

Slide 2
Master the art of DevOps
Master in DevOps Engineering (MDE)

Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.

Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert

Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.

Slide 3
Learn and get certified
AWS Certified DevOps Professional

Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.

previous arrow
next arrow

Docker Error: JOB FOR DOCKER.SERVICE FAILED BECAUSE THE CONTROL PROCESS EXITED WITH ERROR CODE

Spread the Knowledge

[root@localhost ~]# systemctl restart docker

Job for docker.service failed because the control process exited with error code. See “systemctl status docker.service” and “journalctl -xe” for details.

[root@localhost ~]#

[root@localhost ~]# journalctl -xe

Oct 18 12:57:24 localhost.localdomain systemd[1]: Starting Docker Application Container Engine.

— Subject: Unit docker.service has begun start-up

— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit docker.service has begun starting up.

Oct 18 12:57:24 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:24.671424476+05:30″

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.742590614+05:30″

Oct 18 12:57:25 localhost.localdomain systemd[1]: Device dev-disk-by\x2duuid-7acdd2e7\x2dc6c7\x

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.775414831+05:30″

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.785846416+05:30″

Oct 18 12:57:25 localhost.localdomain systemd[1]: docker.service: main process exited, code=exi

Oct 18 12:57:25 localhost.localdomain systemd[1]: Failed to start Docker Application Container

— Subject: Unit docker.service has failed

— Defined-By: systemd

— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit docker.service has failed.

— The result is failed.

Oct 18 12:57:25 localhost.localdomain systemd[1]: Unit docker.service entered failed state.

Oct 18 12:57:25 localhost.localdomain systemd[1]: docker.service failed.

Oct 18 12:57:25 localhost.localdomain polkitd[763]: Unregistered Authentication Agent for unix-

lines 2668-2690/2690 (END)

[root@localhost ~]# systemctl status -l docker.service

? docker.service – Docker Application Container Engine

Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)

Active: failed (Result: exit-code) since Tue 2016-10-18 12:57:25 IST; 6min ago

Docs: https://docs.docker.com

Process: 3547 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE)

Main PID: 3547 (code=exited, status=1/FAILURE)

Oct 18 12:57:24 localhost.localdomain systemd[1]: Starting Docker Application Container Engine…

Oct 18 12:57:24 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:24.671424476+05:30″ level=info msg=”libcontainerd: new containerd process, pid: 3551″

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.742590614+05:30″ level=warning msg=”devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `–storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.”

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.775414831+05:30″ level=warning msg=”devmapper: Base device already exists and has filesystem xfs on it. User specified filesystem  will be ignored.”

Oct 18 12:57:25 localhost.localdomain dockerd[3547]: time=”2016-10-18T12:57:25.785846416+05:30″ level=fatal msg=”Error starting daemon: error initializing graphdriver: \”/var/lib/docker\” contains several valid graphdrivers: devicemapper, overlay; Please cleanup or explicitly choose storage driver (-s <DRIVER>)”

Oct 18 12:57:25 localhost.localdomain systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE

Oct 18 12:57:25 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine.

Oct 18 12:57:25 localhost.localdomain systemd[1]: Unit docker.service entered failed state.

Oct 18 12:57:25 localhost.localdomain systemd[1]: docker.service failed.

Rajesh Kumar