Right, I just realised my pager was cutting of some of the text from journalctl, here is the full text: May 29 11:36:40 linux-9wl3 systemd[1]: Starting Docker Application Container Engine... -- Subject: Unit docker.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has begun starting up. May 29 11:36:40 linux-9wl3 dockerd[6009]: time="2018-05-29T11:36:40.266752347+01:00" level=info msg="[graphdriver] using prior storage driver: btrfs" May 29 11:36:40 linux-9wl3 dockerd[6009]: time="2018-05-29T11:36:40.279617281+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds" May 29 11:36:40 linux-9wl3 dockerd[6009]: time="2018-05-29T11:36:40.279908894+01:00" level=warning msg="Your kernel does not support swap memory limit" May 29 11:36:40 linux-9wl3 dockerd[6009]: time="2018-05-29T11:36:40.279972122+01:00" level=warning msg="Your kernel does not support cgroup rt period" May 29 11:36:40 linux-9wl3 dockerd[6009]: time="2018-05-29T11:36:40.279983947+01:00" level=warning msg="Your kernel does not support cgroup rt runtime" 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'. May 29 11:38:39 linux-9wl3 systemd[1]: Stopped Docker Application Container Engine. -- Subject: Unit docker.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has finished shutting down. On Tue, May 29, 2018 at 11:45 AM, Michael Aquilina <michaelaquilina@gmail.com> wrote:
uname -a Linux linux-9wl3 4.16.8-1-default #1 SMP PREEMPT Wed May 9 10:29:52 UTC 2018 (9269cc1) x86_64 x86_64 x86_64 GNU/Linux
docker -v Docker version 17.09.1-ce, build f4ffd2511ce9
journalctl -u docker.service -xe -- Subject: Unit docker.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit docker.service has begun starting up. May 29 11:38:53 linux-9wl3 dockerd[6894]: time="2018-05-29T11:38:53.414094253+01:00" level=info msg="[graphdriver] using prior storage drive> May 29 11:38:53 linux-9wl3 dockerd[6894]: time="2018-05-29T11:38:53.433686430+01:00" level=info msg="Graph migration to content-addressabili> May 29 11:38:53 linux-9wl3 dockerd[6894]: time="2018-05-29T11:38:53.433909179+01:00" level=warning msg="Your kernel does not support swap me> May 29 11:38:53 linux-9wl3 dockerd[6894]: time="2018-05-29T11:38:53.433943125+01:00" level=warning msg="Your kernel does not support cgroup > May 29 11:38:53 linux-9wl3 dockerd[6894]: time="2018-05-29T11:38:53.433951788+01:00" level=warning msg="Your kernel does not support cgroup > May 29 11:38:53 linux-9wl3 dockerd[6894]: time="2018-05-29T11:38:53.434331950+01:00" level=info msg="Loading containers: start." May 29 11:40:23 linux-9wl3 systemd[1]: docker.service: Start operation timed out. Terminating. May 29 11:40:23 linux-9wl3 dockerd[6894]: time="2018-05-29T11:40:23.437326237+01:00" level=info msg="Processing signal 'terminated'"
Unfurtunately journalctl does not seem to provide much more details than that :/
I tried running dockerd directly with debug mode and got the following message:
sudo dockerd -D DEBU[2018-05-29T11:38:43.432709369+01:00] Listener created for HTTP on unix (/var/run/docker.sock) Failed to connect to containerd. Please make sure containerd is installed in your PATH or you have specified the correct address. Got error: exec: "docker-containerd": executable file not found in $PATH
Searching for `docker-containerd` on my file system with the find utility showed no results.
But I can run containerd as a service with no issues:
sudo systemctl start containerd journalctl -u containerd.service -xe May 29 11:29:38 linux-9wl3 systemd[1]: Started Containerd Standalone OCI Container Daemon. -- Subject: Unit containerd.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit containerd.service has finished starting up. -- -- The start-up result is RESULT.
On Tue, May 29, 2018 at 11:41 AM, Antonio Ojea <aojeagarcia@suse.com> wrote:
The log message says "Your kernel does not support cgroup >" , can you obtain the full line with the "journalctl -xe"command?
Also, what kernel and docker version are you using?
On 29/05/2018 12:16, Michael Aquilina wrote:
Is anyone else experiencing issues starting up the docker daemon?
sudo systemctl start docker Job for docker.service failed because a timeout was exceeded. See "systemctl status docker.service" and "journalctl -xe" for details.
systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled) Active: failed (Result: timeout) since Tue 2018-05-29 11:11:06 BST; 9s ago Docs: http://docs.docker.com Process: 24544 ExecStart=/usr/bin/dockerd --containerd /run/containerd/containerd.sock --add-runtime oci=/usr/sbin/docker-runc $DOCKER_NETW> Main PID: 24544 (code=killed, signal=KILL)
May 29 11:08:06 linux-9wl3 dockerd[24544]: time="2018-05-29T11:08:06.532027695+01:00" level=warning msg="Your kernel does not support cgroup > May 29 11:08:06 linux-9wl3 dockerd[24544]: time="2018-05-29T11:08:06.532087206+01:00" level=warning msg="Your kernel does not support cgroup > May 29 11:08:06 linux-9wl3 dockerd[24544]: time="2018-05-29T11:08:06.533562226+01:00" level=info msg="Loading containers: start." May 29 11:09:36 linux-9wl3 systemd[1]: docker.service: Start operation timed out. Terminating. May 29 11:09:36 linux-9wl3 dockerd[24544]: time="2018-05-29T11:09:36.418326793+01:00" level=info msg="Processing signal 'terminated'" May 29 11:11:06 linux-9wl3 systemd[1]: docker.service: State 'stop-sigterm' timed out. Killing. May 29 11:11:06 linux-9wl3 systemd[1]: docker.service: Killing process 24544 (dockerd) with signal SIGKILL. May 29 11:11:06 linux-9wl3 systemd[1]: docker.service: Main process exited, code=killed, status=9/KILL May 29 11:11:06 linux-9wl3 systemd[1]: docker.service: Failed with result 'timeout'. May 29 11:11:06 linux-9wl3 systemd[1]: Failed to start Docker Application Container Engine.
This was working the last time I tried, so I'm not entirely sure what's going on.
I even tried re-installing docker itself as well as deleting all of /var/lib/docker - but I still get the same issue.
Mike
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Michael Aquilina
-- Michael Aquilina -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org