由于"卷存储元数据库:超时",Docker无法启动

Ida*_*dar 16 centos docker

我已经按照Docker CE for CentOS安装说明进行操作.最初这很有效.在某些时候系统重新启动,现在启动Docker失败.欣赏专家对这件事的看法......

systemctl start docker 生产:

docker.service的作业失败,因为控制进程退出并显示错误代码.有关详细信息,请参阅"systemctl status docker.service"和"journalctl -xe".

systemctl status docker.service 生产:

Apr 21 11:25:23 sec-services-build-1 systemd[1]: Starting Docker Application Container Engine...
Apr 21 11:25:23 sec-services-build-1 dockerd[9693]: time="2017-04-21T11:25:23.370390797+03:00" level=info msg="libcontainerd: previous instance of containerd still alive (8908)"
Apr 21 11:25:23 sec-services-build-1 dockerd[9693]: time="2017-04-21T11:25:23.382492171+03:00" level=warning msg="overlay: the backing xfs filesystem is formatted without d_type support, which leads to incorrect behavior. Reformat the filesystem with ftype=1 to enable d_type support. Running without d_type support will no longer be supported in Docker 17.12."
Apr 21 11:25:23 sec-services-build-1 dockerd[9693]: time="2017-04-21T11:25:23.382547668+03:00" level=info msg="[graphdriver] using prior storage driver: overlay"
Apr 21 11:25:24 sec-services-build-1 dockerd[9693]: Error starting daemon: error while opening volume store metadata database: timeout
Apr 21 11:25:24 sec-services-build-1 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Apr 21 11:25:24 sec-services-build-1 systemd[1]: Failed to start Docker Application Container Engine.
Apr 21 11:25:24 sec-services-build-1 systemd[1]: Unit docker.service entered failed state.
Apr 21 11:25:24 sec-services-build-1 systemd[1]: docker.service failed.
Run Code Online (Sandbox Code Playgroud)

Ida*_*dar 33

从这里:https://github.com/moby/moby/issues/22507

我跑了:

ps axf | grep docker | grep -v grep | awk '{print "kill -9 " $1}' | sudo sh 
Run Code Online (Sandbox Code Playgroud)

然后我可以使用以下命令重启docker:

sudo systemctl start docker
Run Code Online (Sandbox Code Playgroud)


小智 8

步骤1:systemctl status docker(如果docker正在运行)停止docker。

第2步:systemctl停止docker。

步骤3:dockerd


Art*_*fin 7

我在从生产机器复制卷时收到此消息,最终覆盖metadata.db内部/var/lib/docker/volumes,然后崩溃。修复就是这么简单

docker system prune --volumes -f && rm /var/lib/docker/volumes/metadata.db && docker-compose up -d
Run Code Online (Sandbox Code Playgroud)