Arch Linux

stromo

Member

Registered: 2018-05-11

Posts: 12

Docker fails to start

I've had had installed Docker, but never used it. Now I've wanted to try it, but it fails to start:
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: exit-code) since Tue 2018-05-22 17:03:59 CEST; 6s ago
     Docs: https://docs.docker.com
  Process: 21345 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
 Main PID: 21345 (code=exited, status=1/FAILURE)

Mai 22 17:03:59 server systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Mai 22 17:03:59 server systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Mai 22 17:03:59 server systemd[1]: Stopped Docker Application Container Engine.
Mai 22 17:03:59 server systemd[1]: docker.service: Start request repeated too quickly.
Mai 22 17:03:59 server systemd[1]: docker.service: Failed with result 'exit-code'.
Mai 22 17:03:59 server systemd[1]: Failed to start Docker Application Container Engine.

How can I find out where the real problem lies?

firecat53

Member

From: Lake Stevens, WA, USA

Registered: 2007-05-14

Posts: 1,542

Website

Re: Docker fails to start

Start with

journalctl -u docker

. Failing that, run it yourself (see the ExecStart line above) from the command line to see what errors pop up.

---

Github

stromo

Member

Registered: 2018-05-11

Posts: 12

Re: Docker fails to start

It's complaining about missing "OverlayFS" support, despite I'm even using the newest kernel (4.16.10).
Does OverlayFS need the lvm2 service? I have muted it, because I didn't see any purpose for it on my system.

Last edited by stromo (2018-05-24 22:16:30)

firecat53

Member

From: Lake Stevens, WA, USA

Registered: 2007-05-14

Posts: 1,542

Website

Re: Docker fails to start

Here are the requirements for the OverlayFS storage driver. It may be you aren't using the correct filesystem. If not, pick a different storage driver and use a drop-in service file to enable it as described in the wiki.

---

Github

stromo

Member

Registered: 2018-05-11

Posts: 12

Re: Docker fails to start

WARN Error while setting daemon root propagation, this is not generally critical but may cause some functionality to not work or fallback to less desirable behavior  dir=/var/lib/docker error="error getting daemon root's parent mount: Could not find source mount of /var/lib/docker"
Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd

After doing dir="/var/lib/docker" && mount --bind $dir $dir:

Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd

firecat53

Member

From: Lake Stevens, WA, USA

Registered: 2007-05-14

Posts: 1,542

Website

Re: Docker fails to start

You've gotta provide more information... It's not clear at all what filesystem you're using and what exact steps you're taking and why.

---

Github

nhat3o3

Member

Registered: 2020-07-05

Posts: 1

Re: Docker fails to start

Try updating iptables.

sudo pacman -Syu iptables