嘟嘟社区

[疑问] Docker 安装出错求救！！！

moe

本帖最后由 炒土豆丝 于 2022-4-3 02:23 编辑

系统：Debian 11 x64

安装报错。

  1. Job for docker.service failed because the control process exited with error code.
  2. See "systemctl status docker.service" and "journalctl -xe" for details.
  3. invoke-rc.d: initscript docker, action "start" failed.
  4. ● docker.service – Docker Application Container Engine
  5.      Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
  6.      Active: activating (auto-restart) (Result: exit-code) since Sat 2022-04-02 14:00:32 EDT; 3ms ago
  7. TriggeredBy: ● docker.socket
  8.        Docs: https://docs.docker.com
  9.     Process: 59130 ExecStart=/usr/bin/dockerd -H fd:// –containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
  10.    Main PID: 59130 (code=exited, status=1/FAILURE)
  11.         CPU: 84ms
  13. Apr 02 14:00:32 Tokyo768 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
  14. Apr 02 14:00:32 Tokyo768 systemd[1]: docker.service: Failed with result ‘exit-code’.
  15. Apr 02 14:00:32 Tokyo768 systemd[1]: Failed to start Docker Application Container Engine.
  16. dpkg: error processing package docker-ce (–configure):
  17. installed docker-ce package post-installation script subprocess returned error exit status 1
  18. Setting up git (1:2.30.2-1) …
  19. Processing triggers for man-db (2.9.4-2) …
  20. Processing triggers for libc-bin (2.31-13+deb11u2) …
  21. Errors were encountered while processing:
  22. docker-ce
  23. E: Sub-process /usr/bin/dpkg returned an error code (1)

复制代码

运行docker提示：

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

重启提示：

[email protected]:/etc/systemd/system# systemctl start docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Journalctl -xe:

  1. — Journal begins at Tue 2021-12-28 22:34:18 EST, ends at Sat 2022-04-02 14:05:27 EDT. —
  2. Apr 02 14:00:32 Tokyo768 systemd[1]: Starting Docker Application Container Engine…
  3. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.257288199-04:00" level=info msg="Starting up"
  4. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.283097177-04:00" level=info msg="parsed scheme: "unix>
  5. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.283250106-04:00" level=info msg="scheme "unix" not re>
  6. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.283359823-04:00" level=info msg="ccResolverWrapper: sen>
  7. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.283451357-04:00" level=info msg="ClientConn switching b>
  8. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.285138438-04:00" level=info msg="parsed scheme: "unix>
  9. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.285242835-04:00" level=info msg="scheme "unix" not re>
  10. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.285329068-04:00" level=info msg="ccResolverWrapper: sen>
  11. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.285406365-04:00" level=info msg="ClientConn switching b>
  12. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.316903933-04:00" level=info msg="Loading containers: st>
  13. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.325245571-04:00" level=warning msg="Running modprobe br>
  14. Apr 02 14:00:32 Tokyo768 dockerd[59130]: time="2022-04-02T14:00:32.331919746-04:00" level=warning msg="Running iptables –>
  15. Apr 02 14:00:32 Tokyo768 dockerd[59130]: failed to start daemon: Error initializing network controller: error obtaining co>
  16. Apr 02 14:00:32 Tokyo768 dockerd[59130]:  (exit status 4)
  17. Apr 02 14:00:32 Tokyo768 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
  18. Apr 02 14:00:32 Tokyo768 systemd[1]: docker.service: Failed with result ‘exit-code’.
  19. Apr 02 14:00:32 Tokyo768 systemd[1]: Failed to start Docker Application Container Engine.
  20. Apr 02 14:00:34 Tokyo768 systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
  21. Apr 02 14:00:34 Tokyo768 systemd[1]: Stopped Docker Application Container Engine.
  22. Apr 02 14:00:34 Tokyo768 systemd[1]: Starting Docker Application Container Engine…
  23. Apr 02 14:00:34 Tokyo768 dockerd[60631]: time="2022-04-02T14:00:34.570550777-04:00" level=info msg="Starting up"
  24. Apr 02 14:00:34 Tokyo768 dockerd[60631]: time="2022-04-02T14:00:34.573689343-04:00" level=info msg="parsed scheme: "unix>
  25. Apr 02 14:00:34 Tokyo768 dockerd[60631]: time="2022-04-02T14:00:34.573835961-04:00" level=info msg="scheme "unix" not re>

复制代码

  1. failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument

复制代码
直接宝塔Docker管理器 简单快捷

NEET姬 发表于 2022-4-3 02:10
直接宝塔Docker管理器 简单快捷

一样报错
你这是apt安装的？curl -s https://get.docker.com | sudo sh

小二的cat 发表于 2022-4-3 02:14
你这是apt安装的？curl -s https://get.docker.com | sudo sh

对啊，用这个脚本装也一样报这个错。
本帖最后由 asdii 于 2022-4-3 02:23 编辑

记错了
你dd个纯净的系统再用脚本吧

asdii 发表于 2022-4-3 02:21
systemctl enable docker 然后 systemctl start

failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument

好像是网卡的锅？
是不是装了什么防火墙

rem 发表于 2022-4-3 02:26
是不是装了什么防火墙

啥也没装，Vir东京的小白鼠机器。
别用服务启动, 手动命令行启动 /usr/bin/dockerd 查看报错信息