【docker】docker启动失败报错

最新推荐文章于 2025-10-01 19:17:48 发布

原创最新推荐文章于 2025-10-01 19:17:48 发布 · 4.5k 阅读

2 ·

CC 4.0 BY-SA版权

文章标签：

#docker #容器 #运维

docker 专栏收录该内容

8 篇文章

订阅专栏

docker启动失败报错

failed to start daemon: failed to dial “/run/containerd/containerd.sock”: unknown service containerd.services.namespaces.v1.Namespaces: not implemented


root@node01:~# systemctl daemon-reload
^[[Aroot@node01:~# systemctl start docker.service
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
root@node01:~# systemctl status docker.service
× docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Fri 2023-02-24 00:21:03 CST; 1s ago
TriggeredBy: × docker.socket
       Docs: https://docs.docker.com
    Process: 1784 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 1784 (code=exited, status=1/FAILURE)
        CPU: 196ms

2月 24 00:21:03 node01 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
2月 24 00:21:03 node01 systemd[1]: Stopped Docker Application Container Engine.
2月 24 00:21:03 node01 systemd[1]: docker.service: Start request repeated too quickly.
2月 24 00:21:03 node01 systemd[1]: docker.service: Failed with result 'exit-code'.
2月 24 00:21:03 node01 systemd[1]: Failed to start Docker Application Container Engine.
root@node01:~# vi /etc/fstab
root@node01:~# docker ps -a
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
root@node01:~# systemctl restart docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
root@node01:~# journalctl -xeu docker.service
░░ 结果为“failed”。
2月 24 00:25:27 node01 systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit docker.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
2月 24 00:25:27 node01 systemd[1]: Stopped Docker Application Container Engine.
░░ Subject: docker.service 单元已结束停止操作
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ docker.service 单元已结束停止操作。
2月 24 00:25:27 node01 systemd[1]: Starting Docker Application Container Engine...
░░ Subject: docker.service 单元已开始启动
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ docker.service 单元已开始启动。
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.376308380+08:00" level=info msg="Starting up"
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.380746856+08:00" level=info msg="[core] [Channel #1] Channel created" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.380842076+08:00" level=info msg="[core] [Channel #1] original dial target is: \"unix:///run/containerd/containerd.sock\"" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.380953856+08:00" level=info msg="[core] [Channel #1] parsed dial target is: {Scheme:unix Authority: Endpoint:run/containerd/containerd.sock URL:{Scheme:unix Opaque: User: Host: Path:/run/containerd/containerd.sock RawPa>
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.381007952+08:00" level=info msg="[core] [Channel #1] Channel authority set to \"localhost\"" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.381366200+08:00" level=info msg="[core] [Channel #1] Resolver state updated: {\n  \"Addresses\": [\n    {\n      \"Addr\": \"/run/containerd/containerd.sock\",\n      \"ServerName\": \"\",\n      \"Attributes\": {},\n  >
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.381591956+08:00" level=info msg="[core] [Channel #1] Channel switches to new LB policy \"pick_first\"" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.381770948+08:00" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel created" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.381901412+08:00" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.381989384+08:00" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel picks a new address \"/run/containerd/containerd.sock\" to connect" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.382026392+08:00" level=info msg="[core] [Channel #1] Channel Connectivity change to CONNECTING" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.382716872+08:00" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel Connectivity change to READY" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: time="2023-02-24T00:25:27.382811852+08:00" level=info msg="[core] [Channel #1] Channel Connectivity change to READY" module=grpc
2月 24 00:25:27 node01 dockerd[1881]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": unknown service containerd.services.namespaces.v1.Namespaces: not implemented
2月 24 00:25:27 node01 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE

这里的错误原因是unknown service containerd.services.namespaces.v1.Namespaces: not implemented,解决办法为执行如下语句
systemctl stop containerd && systemctl start containerd && systemctl start docker.service