谷姐：我们都是谷歌迷
We are all Google fans
Hi, 请登录   我要注册   找回密码
首页 > 主机域名网站 > Docker 安装出错求救！！！-炒土豆丝

Docker 安装出错求救！！！-炒土豆丝

2022-04-03 分类：主机域名网站 阅读(454) 评论(0) 扫描二维码 隐藏侧边
Rate this post

系统：Debian 11 x64

安装报错。

    Job for docker.service failed because the control process exited with error code.
    See "systemctl status docker.service" and "journalctl -xe" for details.
    invoke-rc.d: initscript docker, action "start" failed.
    ● docker.service - Docker Application Container Engine
    Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Active: activating (auto-restart) (Result: exit-code) since Sat 2022-04-02 14:00:32 EDT; 3ms ago
    TriggeredBy: ● docker.socket
    Docs: https://docs.docker.com
    Process: 59130 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
    Main PID: 59130 (code=exited, status=1/FAILURE)
    CPU: 84ms

    Apr 02 14:00:32 Tokyo768 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
    Apr 02 14:00:32 Tokyo768 systemd[1]: docker.service: Failed with result 'exit-code'.
    Apr 02 14:00:32 Tokyo768 systemd[1]: Failed to start Docker Application Container Engine.
    dpkg: error processing package docker-ce (--configure):
    installed docker-ce package post-installation script subprocess returned error exit status 1
    Setting up git (1:2.30.2-1) ...
    Processing triggers for man-db (2.9.4-2) ...
    Processing triggers for libc-bin (2.31-13+deb11u2) ...
    Errors were encountered while processing:
    docker-ce
    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:

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

    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

热议
2楼 NEET姬 13小时前

直接宝塔Docker管理器 简单快捷

3楼 炒土豆丝 13小时前

直接宝塔Docker管理器 简单快捷

一样报错

4楼 小二的cat 13小时前

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

5楼 炒土豆丝 13小时前

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

对啊，用这个脚本装也一样报这个错。

6楼 asdii 13小时前

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

7楼 炒土豆丝 13小时前

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

好像是网卡的锅？

8楼 rem 13小时前

是不是装了什么防火墙

9楼 炒土豆丝 13小时前

是不是装了什么防火墙

啥也没装，Vir东京的小白鼠机器。

10楼 xayle 13小时前

别用服务启动, 手动命令行启动 /usr/bin/dockerd 查看报错信息

12楼 炒土豆丝 12小时前

别用服务启动, 手动命令行启动 /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 schememodule=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 schememodule=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

13楼 xayle 12小时前

大佬帮忙看看

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

14楼 炒土豆丝 12小时前

系统不完整? unix socket 都不存在.

看来应该是系统的问题，Vir东京提前开机的小白鼠机。

15楼 xayle 12小时前

看来应该是系统的问题，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

执行后再重新启动服务测试

16楼 xayle 12小时前

我刚新装的 debian 11 x64 装 docker, 也没出现这个问题 奇怪.

17楼 xayle 12小时前

看来应该是系统的问题，Vir东京提前开机的小白鼠机。

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

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

18楼 炒土豆丝 11小时前

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

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

可以一启动就报错啊

19楼 炒土豆丝 11小时前

我刚新装的 debian 11 x64 装 docker, 也没出现这个问题 奇怪.

大佬也是VIR东京么

20楼 xayle 11小时前

大佬也是VIR东京么

不是, 下午买的其他家的机器, 才开通.

modinfo bridge
执行上面的命令 看下 签名 key

24楼 xayle 11小时前

uname -a
看下你的系统内核版本

26楼 lewss 2小时前

dd了重新安装还省事一些。

27楼 闪电五连鞭 2小时前

vir debain模板有问题，我DD过的debain11apt安装没问题

28楼 炒土豆丝 1小时前

vir debain模板有问题，我DD过的debain11apt安装没问题

我试过 DD 直接失联了，老哥用哪个脚本DD的？

29楼 闪电五连鞭 25分钟前

我试过 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手动设置一些东西

30楼 Corei7 22分钟前

我试过 DD 直接失联了，老哥用哪个脚本DD的？

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

申明：本文内容由网友收集分享，仅供学习参考使用。如文中内容侵犯到您的利益，请在文章下方留言，本站会第一时间进行处理。

AD：【好消息】Google Voice号码支持自助购买了！

未经谷姐允许不得转载：谷姐靓号网 » Docker 安装出错求救！！！-炒土豆丝
分享到： 生成海报

相关推荐

热门文章

评论 抢沙发

评论前必须登录！

立即登录   注册

买Google Voice认准【谷姐靓号网】

Google Voice靓号列表Google Voice自助购买
切换注册

登录

忘记密码 ?

切换登录

注册

我们将发送一封验证邮件至你的邮箱, 请正确填写以完成账号注册和激活