Docker Community Forums

Share and learn in the Docker community.

Docker Engine is not starting

dockercloud

(bk) #1

Hello ,

I faced disk full issue when creating my image so I followed the steps mentioned and it worked . https://forums.docker.com/t/how-do-i-change-the-docker-image-installation-directory/1169
After that I restarted my ec2 . When I tried a systemctl start docker , it threw e the bellow errors.

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

Then I tried “systemctl status docker.service”

â docker.service - Docker Application Container Engine
** Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)**
** Drop-In: /etc/systemd/system/docker.service.d**
** ââhttp-proxy.conf**
** Active: failed (Result: start-limit) since Thu 2017-11-02 03:38:42 EDT; 40s ago**
** Docs: https://docs.docker.com**
** Process: 7050 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE)**
** Main PID: 7050 (code=exited, status=1/FAILURE)**

Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: Failed to start Docker Application Container Engine.
Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: Unit docker.service entered failed state.
Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: docker.service failed.
Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: docker.service holdoff time over, scheduling restart.
Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: start request repeated too quickly for docker.service
Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: Failed to start Docker Application Container Engine.
Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: Unit docker.service entered failed state.
Nov 02 03:38:42 10-19-32-115.cmp.com systemd[1]: docker.service failed.


How do I change the Docker image installation directory?
(Doncicuto) #2

Hi!
try to start the docker engine service again and then run

journalctl -xe

that will show you the most recent log messages related to the service and you may find what’s preventing the service to start.

Cheers!


(bk) #3

Issue Resolved . After the restart of my ec2 instances the disks which I attached got unmounted . I have to add an entry in /ect/fstab to avoid this in next restart.