Mailinglist Archive: opensuse-factory (536 mails)

< Previous Next >
Re: [opensuse-factory] Issues starting Docker


On 05/29/2018 12:47 PM, Michael Aquilina wrote:
Right, I just realised my pager was cutting of some of the text from
journalctl, here is the full text:


I'm running the latest kernel on my laptop. Here's what I see for
comparison:

● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled;
vendor preset: disabled)
Active: active (running) since Tue 2018-05-29 15:19:17 CEST; 1min 25s ago
Docs: http://docs.docker.com
Main PID: 5979 (dockerd)
Tasks: 14
CGroup: /system.slice/docker.service
└─5979 /usr/bin/dockerd --containerd
/run/containerd/containerd.sock --add-runtime oci=/usr/sbin/docker-runc

May 29 15:19:16 geektop dockerd[5979]:
time="2018-05-29T15:19:16.432782082+02:00" level=warning msg="Your
kernel does not support swap memory limit"
May 29 15:19:16 geektop dockerd[5979]:
time="2018-05-29T15:19:16.432853435+02:00" level=warning msg="Your
kernel does not support cgroup rt period"
May 29 15:19:16 geektop dockerd[5979]:
time="2018-05-29T15:19:16.432876675+02:00" level=warning msg="Your
kernel does not support cgroup rt runtime"
May 29 15:19:16 geektop dockerd[5979]:
time="2018-05-29T15:19:16.433604441+02:00" level=info msg="Loading
containers: start."
May 29 15:19:16 geektop dockerd[5979]:
time="2018-05-29T15:19:16.837999428+02:00" level=info msg="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"
May 29 15:19:17 geektop dockerd[5979]:
time="2018-05-29T15:19:17.101339621+02:00" level=info msg="Loading
containers: done."
May 29 15:19:17 geektop dockerd[5979]:
time="2018-05-29T15:19:17.114568676+02:00" level=info msg="Docker
daemon" commit=f4ffd2511ce9 graphdriver(s)=btrfs version=17.09.1-ce
May 29 15:19:17 geektop dockerd[5979]:
time="2018-05-29T15:19:17.114767454+02:00" level=info msg="Daemon has
completed initialization"
May 29 15:19:17 geektop dockerd[5979]:
time="2018-05-29T15:19:17.139619811+02:00" level=info msg="API listen on
/var/run/docker.sock"
May 29 15:19:17 geektop systemd[1]: Started Docker Application Container
Engine.

From what you posted last:

May 29 11:36:40 linux-9wl3 dockerd[6009]:
time="2018-05-29T11:36:40.280395475+01:00" level=info msg="Loading
containers: start."
May 29 11:37:09 linux-9wl3 dockerd[6009]:
time="2018-05-29T11:37:09.029501073+01:00" level=info msg="Processing
signal 'terminated'"
May 29 11:38:39 linux-9wl3 systemd[1]: docker.service: State
'stop-sigterm' timed out. Killing.
May 29 11:38:39 linux-9wl3 systemd[1]: docker.service: Killing process
6009 (dockerd) with signal SIGKILL.
May 29 11:38:39 linux-9wl3 systemd[1]: docker.service: Main process
exited, code=killed, status=9/KILL
May 29 11:38:39 linux-9wl3 systemd[1]: docker.service: Failed with
result 'timeout'.

I would be interested in finding out what is causing the timeouts.

Jason
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >