Failed to start daemon error while opening volume store metadata database timeout

Can’t start docker on ubuntu (16.04) #281

I am running Ubuntu 16.04 LTS (up to date)

Re-installing docker does not fix the problem

Here is the list of commands / errors (happening after a fresh install, I have no containers)

and from here we are back to 2.

If I restart the computer I go back to 1.

The text was updated successfully, but these errors were encountered:

Well apparently, once installed docker will always start on boot. so the error came from the fact that docker was already running. I won’t detail here the bug chain that let me assume it was not. I am sorry.

I have exactly the same errors, what did you do to fix this problem?

As far as I remeber, I gave up and used a friend’s computer as I only had a small thing to do. Sorry.

I know this is an old question but just in case that someone might have the same problem here is what worked for me.

Step 1:
systemctl status docker

If the docker is running you will get something like:

Step 2:
systemctl stop docker

Step 3:
sudo dockerd

Hope this helps someone else.

Thank u it helped Me..

Muchas gracias funciono.

Thank you very much, it worked right away 🙂 👍

thanos1983, thanks a lot, man!

Thank you very much

so i been waiting for a while after using «sudo dockerd» do i have to do something else? @thanos1983

so i been waiting for a while after using «sudo dockerd» do i have to do something else? @thanos1983

Is the daemon running after?

Check the status:

Is it running? If not try to restart it after:

See if it is working after.

Hope this helps.

Hi.
For me it shows as below
— Welcome to 4Minitz in Docker—*

in 4minitz_settings.json i have even changed the root_url values also but still not able to access from browser.
can anyone suggest me what to be done

Can anyone help me to access the link from outside server ?
Like what all changes we have to do to access from any location and browser.

Can anyone help me to access the link from outside server ?

Like what all changes we have to do to access from any location and browser.

This kind of questions are better asked on relevant forums not on git hub where people report bugs.

I am not sure what are your configurations but from what you describe you need to enable the ipv4/6 forwarder.

Search on the web how to do that based on your version of Linux.

For example for Debian :

Hope this helps.

I know this is an old question but just in case that someone might have the same problem here is what worked for me.

Step 1:
systemctl status docker

If the docker is running you will get something like:

Step 2:
systemctl stop docker

Step 3:
sudo dockerd

Hope this helps someone else.

@thanos1983 2 years later and your solution STILL worked for me, so thank you!

Источник

Error starting daemon: error while opening volume store metadata database: invalid argument #32680

I have install docker in centos 7 vagrant machine. its installed ,but when start the docker its throw Error starting daemon: error while opening volume store metadata database: invalid argument

Vagrant.configure(«2») do |config|

Kernal version: 3.10.0-229.el7.x86_64

docker version:

Start docker below command:

dockerd -g /vagrant/docker

Log Report:

/vagrant is mounted folder via vagrant with in the mount point, I created docker folder the then used to started docker for store docker files , is there any issue?, Docker can access host machine folder via docker?.

reference:

Suggest me what is the issue? how to fix this?.

The text was updated successfully, but these errors were encountered:

Using shared storage to run Docker is generally unsupported.
In the case of this error we are using boltdb to store volume metadata (as are other parts of Docker) and it is likely unable to mmap the file on the virtual box shared folder.

For reference here’s some other reported issues for the exact issue: boltdb/bolt#272

I would also expect that whatever driver used for container storage would fail horribly on vboxfs.

Following the discussion above, I’m closing this issue because this is not a supported setup

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

error during connect: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.27/containers/json: read unix @->/var/run/docker.sock: read: connection reset by peer #435

Expected behavior

Actual behavior

Steps to reproduce the behavior

Output of docker version :

Output of docker info :

Additional environment details (AWS, VirtualBox, physical, etc.)

• AWS Instance — m5.large
• AMI — k8s-1.9-debian-stretch-amd64-hvm-ebs-2018-03-11 (ami-a5c90ed8)

The disk is full, however, I can’t use any docker system prune docker rmi $(docker images -qa) or anything, because all docker xxx results to:

The text was updated successfully, but these errors were encountered:

If the disk is full, and the daemon is no longer able to start because of that, you can’t run docker commands (therefore the docker cli fails to connect with the daemon; it’s not running, or failing to perform its actions).

I don’t think this is a bug, so I’ll close this issue, but feel free to continue the conversation

I have the same issues. But i still have 12G of space left in my SD card. What could be error ?

I had the same problem on a VPS！

I can confirm that it happens on my Raspberry Pi 3 with this data:

And enough free space:

Same problem also for me with raspberry:

I met this problem because of memory not enough, when I increase the memory the problem solved.

I also meet the same issue:

However my host has enough memory and disk.I delete the all the docker directories /var/lib/docker /var/lib/docker-engine /var/lib/docker-shim .Then the docker restart successfully.

1. Ensure that your docker deamon is running: sudo dockerd

• If failed to start daemon: error while opening volume store metadata database: timeout , then sudo rm /var/lib/docker/volumes/metadata.db and retry.
• If failed to start daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid , then sudo rm /var/run/docker.pid and retry.
  then retry.

This is still an issue, I have 16GB free, im assuming it’s some sort of corruption in /var/lib from docker itself (disks are on raid10).

Applying these commands worked for me:

sudo service docker stop &&
sudo rm -rf /var/lib/docker &&
sudo service docker start

Nuking all of Dockers state isn’t a fix, considering this is 3 years old and no progress means I’m not going to consider docker production ready.

considering this is 3 years old and no progress means I’m not going to consider docker production ready.

I agree that nuking Docker state isn’t a fix, but a workaround, so (generally) not recommended. This issue has collected various comments that are unrelated to the original report, but may seem similar. The error during connect error means that the docker client is unable to connect to the daemon, which can have many reasons. The daemon may not have been started, a networking connection could be causing an issue (if the daemon is remote), or any reason the daemon failed to start (logs for the daemon and/or system logs may provide more details in that situation)

So I have this issue to on RPI 4. Enough mem and disk space.
The thing is the docker containers are running:

$ docker info** Containers: 8 Running: 7 Paused: 0 Stopped: 1 Images: 19 Server Version: 18.09.1 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce runc version: 1.0.0

rc6+dfsg1-3 init version: v0.18.0 (expected: fec3683b971d9c3ef73f284f176672c44b448662) Security Options: seccomp Profile: default Kernel Version: 4.19.97-v7l+ Operating System: Raspbian GNU/Linux 10 (buster) OSType: linux Architecture: armv7l CPUs: 4 Total Memory: 3.814GiB Name: raspberrypi ID: DNXZ:KM6S:TRU5:N3XX:2TIQ:47HC:JKL5:KBPD:NJUZ:D43B:NBIE:YKGM Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Username: Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false WARNING: No swap limit support WARNING: No cpu cfs quota support WARNING: No cpu cfs period support **pi@raspberrypi:

$ df -h** Filesystem Size Used Avail Use% Mounted on /dev/root 15G 9.1G 4.4G 68% / devtmpfs 1.8G 0 1.8G 0% /dev tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs 2.0G 9.9M 1.9G 1% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup /dev/mmcblk0p1 253M 53M 200M 21% /boot /dev/sda5 1.9T 1.8T 90G 96% /mnt/usbHDD tmpfs 391M 0 391M 0% /run/user/1000″>

After restart of RPI the containers come up as expected.

Источник

Докер: не удается запустить демон докера, не удается убить контейнер

Итак, у меня возникла проблема, когда Docker решил отказаться от моей виртуальной машины Ubuntu 20.04, размещенной на VirtualBox.

Когда я впервые загружаю свою виртуальную машину, никакие команды докеров не работают. Даже базовые команды, такие как docker help и docker version зависают на неопределенный срок, как и системные команды, взаимодействующие с докером (например, sudo service docker [options] будут зависать).

Я попробовал sudo dockerd —debug и обнаружил, что проблема связана с файлом var/run/docker.pid :

Я пошел и удалил файл docker.pid, затем снова попытался выполнить команду. На этот раз я получил другой вывод, в котором сообщалось, что не удалось запустить демон:

Отсюда команды докеров начинают работать наполовину — например, docker version вернет информацию об ожидаемой версии, но закончится на Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? .

На этом этапе я проверил процесс с помощью service —status-all , который указал, что служба была остановлена ​​( [ — ] docker ). Я проверил детали с service docker status . Это указывало на то, что был контейнер, который не завершился должным образом, что нарушает работу службы:

В этом и заключается проблема — я не могу запустить докер, чтобы убить этот контейнер. Команда требует, чтобы демон Docker был запущен, но все команды, которые я пытался перезапустить, просто зависают на неопределенный срок. И service , и systemctl не работают.

Любая помощь будет принята с благодарностью!

РЕДАКТИРОВАТЬ: после выполнения этих шагов ps -eax | grep docker выдает следующий результат:

Эти процессы продолжают возрождаться с разными PID, когда я пытаюсь их убить, как с помощью sudo kill

Источник

Backgroud:
All docker daemon need to use same images which means one image need storage on each server, it waste too much disk space.
Then, i want to use overlay2 storage and make data-root on cephfs, so that one image could storage one times not X times, and no need to pull X times.

1. install docker-ce(17.09.0-ce) on centos7.4, kernel is 3.10.0-693.el7.x86_64
   Output of docker version :

1. link /var/lib/docker to /cephfs/docker
2. start docker daemon

The first daemon start:

but the second failed, i use debug mdoe to start:

Is it supported?
If not, is there any good partice about similar situation?

The text was updated successfully, but these errors were encountered:

No this is not something you should do; The data-root is designed to be exclusively accessed by a single daemon; if you use a shared filesystem that’s used by multiple daemons, you will run into issues. For example, the daemon tracks which images are in use by a container, and multiple daemons won’t keep track on what’s being used by containers run by other daemons; this could lead to an image being removed by another container. The directory also keeps state (IP-addresses in use, containers running, etc etc). For those reasons you should never share the data-root between daemons.

The «run multiple daemons» mentions this (probably other sections in the documentation as well);

—data-root is the path where persisted data such as images, volumes, and cluster state are stored. The default value is /var/lib/docker . To avoid any conflict with other daemons, set this parameter separately for each daemon.

Please keep in mind that the GitHub issue tracker is not intended as a general support forum,
but for reporting bugs and feature requests. For other type of questions, consider using one of;

I’m closing this issue because this is not a bug, but feel free to continue the conversation 👍

Источник

Can’t start docker on ubuntu (16.04) #281

Comments

efugier commented Apr 15, 2018 •

I am running Ubuntu 16.04 LTS (up to date)

Re-installing docker does not fix the problem

Here is the list of commands / errors (happening after a fresh install, I have no containers)

and from here we are back to 2.

If I restart the computer I go back to 1.

The text was updated successfully, but these errors were encountered:

efugier commented Apr 15, 2018

Well apparently, once installed docker will always start on boot. so the error came from the fact that docker was already running. I won’t detail here the bug chain that let me assume it was not. I am sorry.

lbagathe commented Jan 14, 2019

I have exactly the same errors, what did you do to fix this problem?

efugier commented Jan 15, 2019

As far as I remeber, I gave up and used a friend’s computer as I only had a small thing to do. Sorry.

thanos1983 commented Apr 8, 2019 •

I know this is an old question but just in case that someone might have the same problem here is what worked for me.

Step 1:
systemctl status docker

If the docker is running you will get something like:

Step 2:
systemctl stop docker

Step 3:
sudo dockerd

Hope this helps someone else.

mohanmaniramesh commented Mar 11, 2020

Thank u it helped Me..

Lissen01 commented Sep 15, 2020

Muchas gracias funciono.

yonatansc97 commented Sep 26, 2020

Thank you very much, it worked right away 🙂 👍

galin-s commented Oct 10, 2020

thanos1983, thanks a lot, man!

mamaque commented Nov 11, 2020

Thank you very much

paulcasta commented Nov 21, 2020

so i been waiting for a while after using «sudo dockerd» do i have to do something else? @thanos1983

thanos1983 commented Nov 26, 2020

so i been waiting for a while after using «sudo dockerd» do i have to do something else? @thanos1983

Is the daemon running after?

Check the status:

Is it running? If not try to restart it after:

See if it is working after.

Hope this helps.

wasimdf commented Jun 26, 2021

Hi.
For me it shows as below
— Welcome to 4Minitz in Docker—*

in 4minitz_settings.json i have even changed the root_url values also but still not able to access from browser.
can anyone suggest me what to be done

wasimdf commented Jun 26, 2021

Can anyone help me to access the link from outside server ?
Like what all changes we have to do to access from any location and browser.

thanos1983 commented Jun 26, 2021

Can anyone help me to access the link from outside server ?

Like what all changes we have to do to access from any location and browser.

This kind of questions are better asked on relevant forums not on git hub where people report bugs.

I am not sure what are your configurations but from what you describe you need to enable the ipv4/6 forwarder.

Search on the web how to do that based on your version of Linux.

For example for Debian :

Hope this helps.

pavondunbar commented Sep 14, 2021

I know this is an old question but just in case that someone might have the same problem here is what worked for me.

Step 1:
systemctl status docker

If the docker is running you will get something like:

Step 2:
systemctl stop docker

Step 3:
sudo dockerd

Hope this helps someone else.

@thanos1983 2 years later and your solution STILL worked for me, so thank you!

Источник

Error starting daemon: error while opening volume store metadata database: invalid argument #32680

Comments

Git-Rajkumar commented Apr 18, 2017 •

I have install docker in centos 7 vagrant machine. its installed ,but when start the docker its throw Error starting daemon: error while opening volume store metadata database: invalid argument

Vagrant.configure(«2») do |config|

Kernal version: 3.10.0-229.el7.x86_64

docker version:

Start docker below command:

dockerd -g /vagrant/docker

Log Report:

/vagrant is mounted folder via vagrant with in the mount point, I created docker folder the then used to started docker for store docker files , is there any issue?, Docker can access host machine folder via docker?.

reference:

Suggest me what is the issue? how to fix this?.

The text was updated successfully, but these errors were encountered:

aaronlehmann commented May 18, 2017

cpuguy83 commented May 18, 2017

Using shared storage to run Docker is generally unsupported.
In the case of this error we are using boltdb to store volume metadata (as are other parts of Docker) and it is likely unable to mmap the file on the virtual box shared folder.

For reference here’s some other reported issues for the exact issue: boltdb/bolt#272

I would also expect that whatever driver used for container storage would fail horribly on vboxfs.

thaJeztah commented Jun 4, 2017

Following the discussion above, I’m closing this issue because this is not a supported setup

Footer

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Докер: не удается запустить демон докера, не удается убить контейнер

Итак, у меня возникла проблема, когда Docker решил отказаться от моей виртуальной машины Ubuntu 20.04, размещенной на VirtualBox.

Когда я впервые загружаю свою виртуальную машину, никакие команды докеров не работают. Даже базовые команды, такие как docker help и docker version зависают на неопределенный срок, как и системные команды, взаимодействующие с докером (например, sudo service docker [options] будут зависать).

Я попробовал sudo dockerd —debug и обнаружил, что проблема связана с файлом var/run/docker.pid :

Я пошел и удалил файл docker.pid, затем снова попытался выполнить команду. На этот раз я получил другой вывод, в котором сообщалось, что не удалось запустить демон:

Отсюда команды докеров начинают работать наполовину — например, docker version вернет информацию об ожидаемой версии, но закончится на Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? .

На этом этапе я проверил процесс с помощью service —status-all , который указал, что служба была остановлена ​​( [ — ] docker ). Я проверил детали с service docker status . Это указывало на то, что был контейнер, который не завершился должным образом, что нарушает работу службы:

В этом и заключается проблема — я не могу запустить докер, чтобы убить этот контейнер. Команда требует, чтобы демон Docker был запущен, но все команды, которые я пытался перезапустить, просто зависают на неопределенный срок. И service , и systemctl не работают.

Любая помощь будет принята с благодарностью!

РЕДАКТИРОВАТЬ: после выполнения этих шагов ps -eax | grep docker выдает следующий результат:

Эти процессы продолжают возрождаться с разными PID, когда я пытаюсь их убить, как с помощью sudo kill

Источник

can all docker daemon share one data-root #37008

Comments

daixiang0 commented May 7, 2018 •

Backgroud:
All docker daemon need to use same images which means one image need storage on each server, it waste too much disk space.
Then, i want to use overlay2 storage and make data-root on cephfs, so that one image could storage one times not X times, and no need to pull X times.

1. install docker-ce(17.09.0-ce) on centos7.4, kernel is 3.10.0-693.el7.x86_64
   Output of docker version :

1. link /var/lib/docker to /cephfs/docker
2. start docker daemon

The first daemon start:

but the second failed, i use debug mdoe to start:

Is it supported?
If not, is there any good partice about similar situation?

The text was updated successfully, but these errors were encountered:

thaJeztah commented May 7, 2018

No this is not something you should do; The data-root is designed to be exclusively accessed by a single daemon; if you use a shared filesystem that’s used by multiple daemons, you will run into issues. For example, the daemon tracks which images are in use by a container, and multiple daemons won’t keep track on what’s being used by containers run by other daemons; this could lead to an image being removed by another container. The directory also keeps state (IP-addresses in use, containers running, etc etc). For those reasons you should never share the data-root between daemons.

The «run multiple daemons» mentions this (probably other sections in the documentation as well);

—data-root is the path where persisted data such as images, volumes, and cluster state are stored. The default value is /var/lib/docker . To avoid any conflict with other daemons, set this parameter separately for each daemon.

Please keep in mind that the GitHub issue tracker is not intended as a general support forum,
but for reporting bugs and feature requests. For other type of questions, consider using one of;

I’m closing this issue because this is not a bug, but feel free to continue the conversation 👍

Источник

Процесс Docker не запущен, и какое-либо взаимодействие с докером не выполняется.

В качестве предисловия я запускаю докер в виртуальной машине Ubuntu 20.04 на виртуальном боксе.

Я создал простой сценарий оболочки, чтобы убить любой процесс, запущенный на порту 9042, а затем запустить файл docker-compose. Вот рассматриваемый сценарий:

Однако с тех пор, как я запустил это, моя установка докеров полностью перестала реагировать на какие-либо взаимодействия. Любые команды докера будут зависать на неопределенный срок, пока не будут отменены с помощью Ctrl + C, а любые другие системные команды, использующие докер (например, sudo service docker start ), также будут зависать на неопределенное время.

Если я попытаюсь запустить dockerd , появится сообщение failed to start daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid . Поскольку моя система сообщает, что докер не запущен, я удаляю var/run/docker.pid . Если я попытаюсь снова запустить dockerd, я получаю другое сообщение об ошибке: failed to start daemon: error while opening volume store metadata database: timeout .

На этом этапе некоторые команды докера снова начинают работать. И docker version , и docker help работают, но по-прежнему сообщается, что демон докера не запущен. Попытка запустить docker-compose up в файле docker-compose дает следующий результат:

Другие системные команды, такие как sudo service docker start , по-прежнему зависают на неопределенный срок, пока не будут удалены.

Кто-нибудь знает, в чем может быть проблема здесь?

РЕДАКТИРОВАТЬ: Еще несколько моментов —

Источник

Good morning guys, I’m a beginner with the docker so I don’t know much, but I need to install it. I have a VPS hosting at GoDaddy, I installed the docker following this guide and when I try to start the docker I get the error:

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

Running systemctl status docker.service I get the following result:

[root@ip-107-180-94-5 ~]# systemctl status docker.service -l
● 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
           └─godaddy.conf
   Active: failed (Result: start-limit) since Wed 2020-01-29 06:49:01 MST; 4min 1s ago
     Docs: https://docs.docker.com
  Process: 3708 ExecStartPost=/opt/godaddy/docker/configure-snat (code=exited, status=2)
  Process: 3571 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=0/SUCCESS)
 Main PID: 3571 (code=exited, status=0/SUCCESS)

Jan 29 06:48:59 ip-107-180-94-5.ip.secureserver.net systemd[1]: Failed to start Docker Application Container Engine.
Jan 29 06:48:59 ip-107-180-94-5.ip.secureserver.net systemd[1]: Unit docker.service entered failed state.
Jan 29 06:48:59 ip-107-180-94-5.ip.secureserver.net systemd[1]: docker.service failed.
Jan 29 06:49:01 ip-107-180-94-5.ip.secureserver.net systemd[1]: docker.service holdoff time over, scheduling restart.
Jan 29 06:49:01 ip-107-180-94-5.ip.secureserver.net systemd[1]: Stopped Docker Application Container Engine.
Jan 29 06:49:01 ip-107-180-94-5.ip.secureserver.net systemd[1]: start request repeated too quickly for docker.service
Jan 29 06:49:01 ip-107-180-94-5.ip.secureserver.net systemd[1]: Failed to start Docker Application Container Engine.
Jan 29 06:49:01 ip-107-180-94-5.ip.secureserver.net systemd[1]: Unit docker.service entered failed state.
Jan 29 06:49:01 ip-107-180-94-5.ip.secureserver.net systemd[1]: docker.service failed.

Running journalctl -xe I get the following result:

[root@ip-107-180-94-5 ~]# journalctl -xe-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished starting up.--
-- The start-up result is done.Jan 29 07:10:01 ip-107-180-94-5.ip.secureserver.net systemd[1]: Started Session 11104 of user root.-- Subject: Unit session-11104.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel--
-- Unit session-11104.scope has finished starting up.
--
-- The start-up result is done.Jan 29 07:10:01 ip-107-180-94-5.ip.secureserver.net systemd[1]: Started Session 11105 of user root.
-- Subject: Unit session-11105.scope has finished start-up
-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit session-11105.scope has finished starting up.
--
-- The start-up result is done.
Jan 29 07:10:01 ip-107-180-94-5.ip.secureserver.net CROND[31560]: (root) CMD (/usr/local/cpanel/scripts/dcpumon-wr
Jan 29 07:10:01 ip-107-180-94-5.ip.secureserver.net CROND[31561]: (root) CMD (/usr/lib64/sa/sa1 1 1)

I followed some posts from people with the same error to anything I do works.
I managed to get another result by running dockerd --debug, it stops on the following line and I need to abort the command:

INFO[2020-01-29T07:14:39.129935890-07:00] API listen on /var/run/docker.sock

After that if I run systemctl start docker it gets stuck without giving back and I need to abort the command again, then after that I check the status withsystemctl status docker.service -l generates the following result:

● 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
           └─godaddy.conf
   Active: activating (start-post) since Wed 2020-01-29 07:17:17 MST; 1min 39s ago
     Docs: https://docs.docker.com
 Main PID: 32176 (dockerd);         : 32313 (configure-snat)
    Tasks: 15
   Memory: 39.6M
   CGroup: /system.slice/docker.service
           ├─32176 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
           └─control
             ├─ 5261 sleep 0.1
             └─32313 /bin/bash /opt/godaddy/docker/configure-snat

Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: Cannot connect to the Docker daemon atunix:///var/run/docker.sock. Is the docker daemon running?
Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: waiting for docker bridge...
Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: Cannot connect to the Docker daemon atunix:///var/run/docker.sock. Is the docker daemon running?
Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: waiting for docker bridge...
Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: Cannot connect to the Docker daemon atunix:///var/run/docker.sock. Is the docker daemon running?
Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: waiting for docker bridge...
Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: Cannot connect to the Docker daemon atunix:///var/run/docker.sock. Is the docker daemon running?
Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: waiting for docker bridge...
Jan 29 07:18:56 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: Cannot connect to the Docker daemon atunix:///var/run/docker.sock. Is the docker daemon running?
Jan 29 07:18:57 ip-107-180-94-5.ip.secureserver.net configure-snat[32313]: waiting for docker bridge...

Following other tips I ran the dockerd command and generated the result:

WARN[2020-01-29T07:20:27.025438855-07:00] The "graph" config file option is deprecated. Please use "data-root" instead.
INFO[2020-01-29T07:20:27.025693705-07:00] Starting up
failed to start daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid

So I delete the .pid file and the result changes to:

WARN[2020-01-29T07:22:44.060324431-07:00] The "graph" config file option is deprecated. Please use "data-root" instead.
INFO[2020-01-29T07:22:44.061145504-07:00] Starting up
INFO[2020-01-29T07:22:44.064401028-07:00] parsed scheme: "unix"                         module=grpc
INFO[2020-01-29T07:22:44.064684277-07:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2020-01-29T07:22:44.064771804-07:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0  <nil>}] <nil>}  module=grpc
INFO[2020-01-29T07:22:44.064814177-07:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2020-01-29T07:22:44.070245283-07:00] parsed scheme: "unix"                         module=grpc
INFO[2020-01-29T07:22:44.070333997-07:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2020-01-29T07:22:44.070364847-07:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0  <nil>}] <nil>}  module=grpc
INFO[2020-01-29T07:22:44.070390331-07:00] ClientConn switching balancer to "pick_first"  module=grpc
WARN[2020-01-29T07:22:44.071893568-07:00] [graphdriver] WARNING: the overlay storage-driver is deprecated, and will be removed in a future release
failed to start daemon: error while opening volume store metadata database: timeout

And after that I couldn’t go on to anything else, I already reinstalled the docker about 2 times and still nothing. Can anyone help me? I’m using the CentOS 7 distribution.