全球主机交流论坛

标题: Docker 安装出错求救！！！ [打印本页]
作者: 炒土豆丝    时间: 2022-4-3 02:02
标题: Docker 安装出错求救！！！
本帖最后由 炒土豆丝 于 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?

重启提示：

root@Tokyo768:/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
复制代码
作者: NEET姬    时间: 2022-4-3 02:10
直接宝塔Docker管理器 简单快捷
作者: 炒土豆丝    时间: 2022-4-3 02:11
NEET姬 发表于 2022-4-3 02:10
直接宝塔Docker管理器 简单快捷

一样报错
作者: 小二的cat    时间: 2022-4-3 02:14
你这是apt安装的？curl -s https://get.docker.com | sudo sh
作者: 炒土豆丝    时间: 2022-4-3 02:18
小二的cat 发表于 2022-4-3 02:14
你这是apt安装的？curl -s https://get.docker.com | sudo sh

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

记错了
你dd个纯净的系统再用脚本吧
作者: 炒土豆丝    时间: 2022-4-3 02:23
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
是不是装了什么防火墙
作者: 炒土豆丝    时间: 2022-4-3 02:31
rem 发表于 2022-4-3 02:26
是不是装了什么防火墙

啥也没装，Vir东京的小白鼠机器。
作者: xayle    时间: 2022-4-3 02:34
别用服务启动, 手动命令行启动 /usr/bin/dockerd 查看报错信息
作者: 好鸭    时间: 2022-4-3 02:34
curl -L get.docker.com|bash
作者: 炒土豆丝    时间: 2022-4-3 03:09
xayle 发表于 2022-4-3 02:34
别用服务启动, 手动命令行启动 /usr/bin/dockerd 查看报错信息

大佬帮忙看看

INFO[2022-04-02T15:09:23.065730932-04:00] Starting up                                 
INFO[2022-04-02T15:09:23.066422959-04:00] parsed scheme: "unix"                         module=grpc
INFO[2022-04-02T15:09:23.066499493-04:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2022-04-02T15:09:23.066568402-04:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock  <nil> 0 <nil>}] <nil> <nil>}  module=grpc
INFO[2022-04-02T15:09:23.066630799-04:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2022-04-02T15:09:23.067394151-04:00] parsed scheme: "unix"                         module=grpc
INFO[2022-04-02T15:09:23.067453523-04:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2022-04-02T15:09:23.067502294-04:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock  <nil> 0 <nil>}] <nil> <nil>}  module=grpc
INFO[2022-04-02T15:09:23.067536919-04:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2022-04-02T15:09:23.079010471-04:00] [graphdriver] using prior storage driver: overlay2
INFO[2022-04-02T15:09:23.080625430-04:00] Loading containers: start.                  
WARN[2022-04-02T15:09:23.089744464-04:00] Running modprobe bridge br_netfilter failed with message: modprobe: ERROR: could not insert 'bridge': Key was rejected by service
modprobe: ERROR: could not insert 'br_netfilter': Key was rejected by service
insmod /lib/modules/5.10.0-10-amd64/kernel/net/bridge/bridge.ko
insmod /lib/modules/5.10.0-10-amd64/kernel/net/bridge/bridge.ko
, error: exit status 1
WARN[2022-04-02T15:09:23.093554721-04:00] Running iptables --wait -t nat -L -n failed with message: `iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument`, error: exit status 4
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
作者: xayle    时间: 2022-4-3 03:19
本帖最后由 xayle 于 2022-4-3 03:24 编辑
炒土豆丝 发表于 2022-4-3 03:09
大佬帮忙看看


https://forums.docker.com/t/failing-to-start-dockerd-failed-to-create-nat-chain-docker/78269

转换为传统模式

sudo update-alternatives --set iptables /usr/sbin/iptables-legacy
sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
作者: 炒土豆丝    时间: 2022-4-3 03:20
xayle 发表于 2022-4-3 03:19
系统不完整? unix socket 都不存在.

看来应该是系统的问题，Vir东京提前开机的小白鼠机。
作者: xayle    时间: 2022-4-3 03:24
本帖最后由 xayle 于 2022-4-3 03:26 编辑
炒土豆丝 发表于 2022-4-3 03:20
看来应该是系统的问题，Vir东京提前开机的小白鼠机。


https://forums.docker.com/t/failing-to-start-dockerd-failed-to-create-nat-chain-docker/78269

转换为传统模式

sudo update-alternatives --set iptables /usr/sbin/iptables-legacy
sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy


执行后再重新启动服务测试
作者: xayle    时间: 2022-4-3 03:29
我刚新装的 debian 11 x64 装 docker, 也没出现这个问题 奇怪.
作者: xayle    时间: 2022-4-3 03:34
炒土豆丝 发表于 2022-4-3 03:20
看来应该是系统的问题，Vir东京提前开机的小白鼠机。

unix:///run/containerd/containerd.sock

这个提示未注册是容器服务没有启动成功.
作者: 炒土豆丝    时间: 2022-4-3 03:51
xayle 发表于 2022-4-3 03:34
unix:///run/containerd/containerd.sock

这个提示未注册是容器服务没有启动成功.

可以一启动就报错啊
作者: 炒土豆丝    时间: 2022-4-3 03:52
xayle 发表于 2022-4-3 03:29
我刚新装的 debian 11 x64 装 docker, 也没出现这个问题 奇怪.

大佬也是VIR东京么
作者: xayle    时间: 2022-4-3 03:55
炒土豆丝 发表于 2022-4-3 03:52
大佬也是VIR东京么

不是, 下午买的其他家的机器, 才开通.
作者: sdqu    时间: 2022-4-3 03:55
google一下
scheme "unix" not registered, fallback to default scheme  module=grpc
很多都是在讲这个，应该总有一个适合你
作者: 炒土豆丝    时间: 2022-4-3 03:57
xayle 发表于 2022-4-3 03:24
https://forums.docker.com/t/failing-to-start-dockerd-failed-to-create-nat-chain-docker/78269

转换 ...

转换后少报了一条错误

  1. WARN[2022-04-02T15:56:11.074450966-04:00] Running modprobe bridge br_netfilter failed with message: modprobe: ERROR: could not insert 'bridge': Key was rejected by service
  2. modprobe: ERROR: could not insert 'br_netfilter': Key was rejected by service
  3. insmod /lib/modules/5.10.0-10-amd64/kernel/net/bridge/bridge.ko
  4. insmod /lib/modules/5.10.0-10-amd64/kernel/net/bridge/bridge.ko
  5. , error: exit status 1
  6. INFO[2022-04-02T15:56:11.090697944-04:00] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address
  7. failed to start daemon: Error initializing network controller: Error creating default "bridge" network: package not installed
复制代码
作者: xayle    时间: 2022-4-3 04:02
炒土豆丝 发表于 2022-4-3 03:57
转换后少报了一条错误

报错信息 bridge 模块 key 被拒绝, 不能加载.


看下下 新装的几个 都是
  1. 4B:6E:F5:AB:CA:66:98:25:17:8E:05:2C:84:66:7C:CB:C0:53:1F:8C
复制代码


modinfo bridge
执行上面的命令 看下 签名 key
作者: xayle    时间: 2022-4-3 04:05
uname -a
看下你的系统内核版本
作者: 炒土豆丝    时间: 2022-4-3 04:06
xayle 发表于 2022-4-3 04:02
报错信息 bridge 模块 key 被拒绝, 不能加载.

Linux Tokyo768 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 GNU/Linux

  1. filename:       /lib/modules/5.10.0-10-amd64/kernel/net/bridge/bridge.ko
  2. alias:          rtnl-link-bridge
  3. version:        2.3
  4. license:        GPL
  5. srcversion:     5E154AB40AC717603A73F15
  6. depends:        stp,llc
  7. retpoline:      Y
  8. intree:         Y
  9. name:           bridge
  10. vermagic:       5.10.0-10-amd64 SMP mod_unload modversions
  11. sig_id:         PKCS#7
  12. signer:         Debian Secure Boot CA
  13. sig_key:        4B:6E:F5:AB:CA:66:98:25:17:8E:05:2C:84:66:7C:CB:C0:53:1F:8C
  14. sig_hashalgo:   sha256
  15. signature:      22:F3:30:FC:CA:92:92:B4:FD:40:01:9C:88:39:32:C9:29:99:32:E9:
  16.                 15:0A:FC:1E:8C:EE:DA:46:51:73:21:F0:8E:21:D6:56:FF:1B:79:B9:
  17.                 99:D5:AB:26:E3:32:12:EC:79:DF:11:61:77:F1:96:AF:D2:56:44:81:
  18.                 75:D5:7F:A7:FE:39:57:FA:35:3B:D7:17:5C:22:BA:E2:E3:62:1C:BA:
  19.                 EA:01:54:28:FB:9D:36:92:B8:08:EB:00:DF:F2:03:CE:6B:6A:5E:FC:
  20.                 BF:8B:EF:D8:0F:8C:C5:C0:51:45:26:5D:21:E9:E4:23:33:21:A8:57:
  21.                 30:96:FF:0B:CE:76:F9:4A:AC:CA:E0:8C:48:32:97:A1:60:94:49:B5:
  22.                 79:69:A4:23:F5:DD:D7:CF:9C:D9:1D:B3:50:6B:F1:7C:73:8D:A6:6B:
  23.                 A1:04:75:D2:E3:7C:21:89:FA:DA:0F:AB:0F:32:0E:79:A9:46:07:03:
  24.                 C3:5E:2A:AD:B5:53:43:52:64:AF:9F:88:4B:C6:B3:57:8D:69:9A:A4:
  25.                 E0:52:4A:E4:85:BC:4D:F0:5B:A5:34:D5:FA:4F:94:E8:00:B5:74:18:
  26.                 37:21:55:70:0F:38:A3:1F:C2:E2:CD:08:5D:41:7B:5E:A4:8F:43:D7:
  27.                 4B:CA:E9:9D:44:7A:04:7A:29:12:23:12:D5:71:6B:A5
  28. root@Tokyo768:~#
复制代码
作者: lewss    时间: 2022-4-3 13:31
dd了重新安装还省事一些。
作者: 闪电五连鞭    时间: 2022-4-3 13:33
vir debain模板有问题，我DD过的debain11apt安装没问题
作者: 炒土豆丝    时间: 2022-4-3 13:50
闪电五连鞭 发表于 2022-4-3 13:33
vir debain模板有问题，我DD过的debain11apt安装没问题

我试过 DD 直接失联了，老哥用哪个脚本DD的？
作者: 闪电五连鞭    时间: 2022-4-3 15:20
炒土豆丝 发表于 2022-4-3 13:50
我试过 DD 直接失联了，老哥用哪个脚本DD的？

bash <(wget --no-check-certificate -qO- 'https://moeclub.org/attachment/LinuxShell/InstallNET.sh') -d 11 -v 64 -a -firmware -p 自定义密码 这个是直接dd debain11不过还是要进vnc手动设置一些东西
作者: Corei7    时间: 2022-4-3 15:24
炒土豆丝 发表于 2022-4-3 13:50
我试过 DD 直接失联了，老哥用哪个脚本DD的？

DD， 解决docker安装问题，用萌卡大佬的脚本，期间可能会offline，去面板重启就行了，可能会offline几次，看vnc掉了就去重启



欢迎光临 全球主机交流论坛 (https://fd.vvwvv.eu.org/) Powered by Discuz! X3.4