lsward
Posts: 6
Joined: Sun Jul 23, 2017 3:11 pm

Why is docker not starting?

Wed Jan 31, 2018 4:42 pm

These are the steps I followed:

Code: Select all

sudo eopkg install docker
sudo systemctl enable docker
sudo systemctl start docker
I always get this message:

Code: Select all

Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
The first time, I just did a bunch of system wide updates hoping that would take care of the problem. The second time I looked at systemctl status docker.service:

Code: Select all

docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor pres>
Active: failed (Result: exit-code) since Wed 2018-01-31 10:14:59 EST; 13min >
Docs: https://docs.docker.com
Process: 2779 ExecStart=/usr/bin/dockerd --storage-driver=overlay -H fd:// (c>
Main PID: 2779 (code=exited, status=1/FAILURE)
and I tried looking at journalctl -xe nothing showed up about docker.

The weird thing is that docker use to work on my laptop, but now I can’t figure out what is going on. Any suggestions on what steps I should take next?

sunnyflunk
Development Team
Posts: 2895
Joined: Sun Mar 13, 2016 11:35 pm

Re: Why is docker not starting?

Fri Feb 02, 2018 4:14 am

I just tried it (and bear in mind I've never used it before), and the service appears to work without issue
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
Active: active (running) since Fri 2018-02-02 14:11:19 AEDT; 5s ago
Docs: https://docs.docker.com
Main PID: 21250 (dockerd)
Tasks: 20 (limit: 4915)
CGroup: /system.slice/docker.service
21250 /usr/bin/dockerd --storage-driver=overlay -H fd://
21257 docker-containerd --config /var/run/docker/containerd/containerd.toml

lsward
Posts: 6
Joined: Sun Jul 23, 2017 3:11 pm

Re: Why is docker not starting?

Fri Feb 02, 2018 9:09 pm

sunnyflunk wrote:
Fri Feb 02, 2018 4:14 am
I just tried it (and bear in mind I've never used it before), and the service appears to work without issue
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: enabled)
Active: active (running) since Fri 2018-02-02 14:11:19 AEDT; 5s ago
Docs: https://docs.docker.com
Main PID: 21250 (dockerd)
Tasks: 20 (limit: 4915)
CGroup: /system.slice/docker.service
21250 /usr/bin/dockerd --storage-driver=overlay -H fd://
21257 docker-containerd --config /var/run/docker/containerd/containerd.toml
Yeah...I see that. Not sure what I should do to figure out why it's not working. Any advise?

lsward
Posts: 6
Joined: Sun Jul 23, 2017 3:11 pm

Re: Why is docker not starting?

Fri Feb 02, 2018 9:24 pm

Maybe this will help?

Code: Select all

lsward@lsward ~ $ sudo dockerd &
[1] 7023
lsward@lsward ~ $ INFO[2018-02-02T15:22:34.084768165-05:00] libcontainerd: started new docker-containerd process  pid=7035
INFO[0000] starting containerd                           module=containerd revision=2b8ed96d2a422bf205adcdfa05272dc12c81613b version=v1.0.0-beta.3
INFO[0000] changing OOM score to -500                    module=containerd
INFO[0000] loading plugin "io.containerd.content.v1.content"...  module=containerd type=io.containerd.content.v1
INFO[0000] loading plugin "io.containerd.snapshotter.v1.btrfs"...  module=containerd type=io.containerd.snapshotter.v1
WARN[0000] failed to load plugin io.containerd.snapshotter.v1.btrfs  error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module=containerd
INFO[0000] loading plugin "io.containerd.snapshotter.v1.overlayfs"...  module=containerd type=io.containerd.snapshotter.v1
INFO[0000] loading plugin "io.containerd.metadata.v1.bolt"...  module=containerd type=io.containerd.metadata.v1
WARN[0000] could not use snapshotter btrfs in metadata plugin  error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module="containerd/io.containerd.metadata.v1.bolt"
INFO[0000] loading plugin "io.containerd.differ.v1.walking"...  module=containerd type=io.containerd.differ.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.containers"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.content"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.diff"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.events"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.healthcheck"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.images"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.leases"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.namespaces"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.snapshots"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.monitor.v1.cgroups"...  module=containerd type=io.containerd.monitor.v1
INFO[0000] loading plugin "io.containerd.runtime.v1.linux"...  module=containerd type=io.containerd.runtime.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.tasks"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.version"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.introspection"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd-debug.sock" module="containerd/debug"
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd.sock" module="containerd/grpc"
INFO[0000] containerd successfully booted in 0.002531s   module=containerd
INFO[2018-02-02T15:22:34.116358951-05:00] [graphdriver] using prior storage driver: overlay 
Error starting daemon: error while opening volume store metadata database: timeout

This is the message I see most often:

Code: Select all

lsward@lsward ~ $ docker images
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

sunnyflunk
Development Team
Posts: 2895
Joined: Sun Mar 13, 2016 11:35 pm

Re: Why is docker not starting?

Fri Feb 09, 2018 9:30 am

lsward wrote:
Fri Feb 02, 2018 9:24 pm
Maybe this will help?

Code: Select all

lsward@lsward ~ $ sudo dockerd &
[1] 7023
lsward@lsward ~ $ INFO[2018-02-02T15:22:34.084768165-05:00] libcontainerd: started new docker-containerd process  pid=7035
INFO[0000] starting containerd                           module=containerd revision=2b8ed96d2a422bf205adcdfa05272dc12c81613b version=v1.0.0-beta.3
INFO[0000] changing OOM score to -500                    module=containerd
INFO[0000] loading plugin "io.containerd.content.v1.content"...  module=containerd type=io.containerd.content.v1
INFO[0000] loading plugin "io.containerd.snapshotter.v1.btrfs"...  module=containerd type=io.containerd.snapshotter.v1
WARN[0000] failed to load plugin io.containerd.snapshotter.v1.btrfs  error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module=containerd
INFO[0000] loading plugin "io.containerd.snapshotter.v1.overlayfs"...  module=containerd type=io.containerd.snapshotter.v1
INFO[0000] loading plugin "io.containerd.metadata.v1.bolt"...  module=containerd type=io.containerd.metadata.v1
WARN[0000] could not use snapshotter btrfs in metadata plugin  error="path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module="containerd/io.containerd.metadata.v1.bolt"
INFO[0000] loading plugin "io.containerd.differ.v1.walking"...  module=containerd type=io.containerd.differ.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.containers"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.content"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.diff"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.events"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.healthcheck"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.images"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.leases"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.namespaces"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.snapshots"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.monitor.v1.cgroups"...  module=containerd type=io.containerd.monitor.v1
INFO[0000] loading plugin "io.containerd.runtime.v1.linux"...  module=containerd type=io.containerd.runtime.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.tasks"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.version"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.introspection"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd-debug.sock" module="containerd/debug"
INFO[0000] serving...                                    address="/var/run/docker/containerd/docker-containerd.sock" module="containerd/grpc"
INFO[0000] containerd successfully booted in 0.002531s   module=containerd
INFO[2018-02-02T15:22:34.116358951-05:00] [graphdriver] using prior storage driver: overlay 
Error starting daemon: error while opening volume store metadata database: timeout

This is the message I see most often:

Code: Select all

lsward@lsward ~ $ docker images
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Would suggest validating the installed packages by running the command here (at the top)

https://solus-project.com/articles/trou ... ooting/en/

Then run this to ensure services and users are setup properly.

Code: Select all

sudo usysconf run -f

Return to “Other Questions”