Docker守护程序在启动后不久就被杀死了

问题描述 投票:1回答:1

我有一台运行Ubuntu 18.04.2 LTS的服务器,带有最新的更新。我使用https://docs.docker.com/install/linux/docker-ce/ubuntu/的教程使用repo安装了docker-ce

在启动后的短时间内,docker守护程序以某种方式被杀死。为了调试,我跑了

/usr/bin/dockerd

以root身份获取日志输出:

root@hostname ~ # /usr/bin/dockerd
INFO[2019-02-21T17:20:15.233508941+01:00] systemd-resolved is running, so using resolvconf: /run/systemd/resolve/resolv.conf
INFO[2019-02-21T17:20:15.235533437+01:00] parsed scheme: "unix"                         module=grpc
INFO[2019-02-21T17:20:15.235562227+01:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2019-02-21T17:20:15.235594491+01:00] parsed scheme: "unix"                         module=grpc
INFO[2019-02-21T17:20:15.235601292+01:00] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2019-02-21T17:20:15.239064773+01:00] ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0  <nil>}]  module=grpc
INFO[2019-02-21T17:20:15.239098425+01:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2019-02-21T17:20:15.239155494+01:00] pickfirstBalancer: HandleSubConnStateChange: 0xc42018d430, CONNECTING  module=grpc
INFO[2019-02-21T17:20:15.239321579+01:00] pickfirstBalancer: HandleSubConnStateChange: 0xc42018d430, READY  module=grpc
INFO[2019-02-21T17:20:15.240106192+01:00] ccResolverWrapper: sending new addresses to cc: [{unix:///run/containerd/containerd.sock 0  <nil>}]  module=grpc
INFO[2019-02-21T17:20:15.240142826+01:00] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2019-02-21T17:20:15.240193046+01:00] pickfirstBalancer: HandleSubConnStateChange: 0xc4207c2120, CONNECTING  module=grpc
INFO[2019-02-21T17:20:15.240315657+01:00] pickfirstBalancer: HandleSubConnStateChange: 0xc4207c2120, READY  module=grpc
INFO[2019-02-21T17:20:15.243221391+01:00] [graphdriver] using prior storage driver: overlay2 
INFO[2019-02-21T17:20:15.275042317+01:00] Graph migration to content-addressability took 0.00 seconds 
WARN[2019-02-21T17:20:15.275313782+01:00] Your kernel does not support swap memory limit 
WARN[2019-02-21T17:20:15.275355076+01:00] Your kernel does not support cgroup rt period 
WARN[2019-02-21T17:20:15.275369332+01:00] Your kernel does not support cgroup rt runtime 
INFO[2019-02-21T17:20:15.275785076+01:00] Loading containers: start.                   
INFO[2019-02-21T17:20:16.335203892+01: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 
INFO[2019-02-21T17:20:16.683066803+01:00] Loading containers: done.                    
INFO[2019-02-21T17:20:16.835625998+01:00] Docker daemon                                 commit=6247962 graphdriver(s)=overlay2 version=18.09.2
INFO[2019-02-21T17:20:16.835701364+01:00] Daemon has completed initialization          
INFO[2019-02-21T17:20:16.842961863+01:00] API listen on /var/run/docker.sock             
Killed

正如你所看到的,有两个警告(我认为它们是不相关的)和一条关于杀戮的消息。守护进程的运行时间大约是一分钟。

我之前在这台机器上安装了docker(使用docker.io),但我清除了所有数据包,删除了/ var,/ etc和/ home和/ run中所有与docker相关的文件,并对任何文件执行了系统范围的搜索与*docker*在其中。这个问题仍然存在。我怎样才能进一步调试并找出docker守护进程一直被杀的原因?

linux docker crash systemd
1个回答
0
投票

检查/var/log/kern.log以查看docker守护程序被杀的原因。如果它是关于触发的OOM杀手(内存不足杀手),则系统上没有足够的内存。添加更多RAM或交换内存。

© www.soinside.com 2019 - 2024. All rights reserved.