Cli: Failed to start Docker Application Container Engine. dockerd is not starting up.

Created on 11 Aug 2019  ·  3Comments  ·  Source: docker/cli

_I'm Not bale to start Docker deamon on my system_. I've tried a lot
While running this command sudo /usr/bin/dockerd -H unix:// -H tcp://0.0.0.0:2736
Error is :

INFO[2019-08-11T12:33:28.014891347+05:30] Starting up                                  
WARN[2019-08-11T12:33:28.055712897+05:30] [!] DON'T BIND ON ANY IP ADDRESS WITHOUT setting --tlsverify IF YOU DON'T KNOW WHAT YOU'RE DOING [!] 
INFO[2019-08-11T12:33:28.056828188+05:30] detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf 
INFO[2019-08-11T12:33:28.163263654+05:30] parsed scheme: "unix"                         module=grpc
INFO[2019-08-11T12:33:28.163393851+05:30] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2019-08-11T12:33:28.163491789+05:30] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0  <nil>}] }  module=grpc
INFO[2019-08-11T12:33:28.163553280+05:30] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2019-08-11T12:33:28.177835197+05:30] pickfirstBalancer: HandleSubConnStateChange: 0xc0008248b0, CONNECTING  module=grpc
INFO[2019-08-11T12:33:28.178304336+05:30] blockingPicker: the picked transport is not ready, loop back to repick  module=grpc
INFO[2019-08-11T12:33:28.277757380+05:30] pickfirstBalancer: HandleSubConnStateChange: 0xc0008248b0, READY  module=grpc
INFO[2019-08-11T12:33:28.307256890+05:30] parsed scheme: "unix"                         module=grpc
INFO[2019-08-11T12:33:28.307363806+05:30] scheme "unix" not registered, fallback to default scheme  module=grpc
INFO[2019-08-11T12:33:28.307429100+05:30] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0  <nil>}] }  module=grpc
INFO[2019-08-11T12:33:28.307467930+05:30] ClientConn switching balancer to "pick_first"  module=grpc
INFO[2019-08-11T12:33:28.307702267+05:30] pickfirstBalancer: HandleSubConnStateChange: 0xc000824d70, CONNECTING  module=grpc
INFO[2019-08-11T12:33:28.307797788+05:30] blockingPicker: the picked transport is not ready, loop back to repick  module=grpc
INFO[2019-08-11T12:33:28.309296205+05:30] pickfirstBalancer: HandleSubConnStateChange: 0xc000824d70, READY  module=grpc
INFO[2019-08-11T12:33:28.690331742+05:30] [graphdriver] using prior storage driver: overlay2 
WARN[2019-08-11T12:33:29.033660669+05:30] Your kernel does not support swap memory limit 
WARN[2019-08-11T12:33:29.033755548+05:30] Your kernel does not support cgroup rt period 
WARN[2019-08-11T12:33:29.033781272+05:30] Your kernel does not support cgroup rt runtime 
WARN[2019-08-11T12:33:29.033802421+05:30] Your kernel does not support cgroup blkio weight 
WARN[2019-08-11T12:33:29.033832885+05:30] Your kernel does not support cgroup blkio weight_device 
INFO[2019-08-11T12:33:29.036414847+05:30] Loading containers: start.                   
INFO[2019-08-11T12:33:31.465795155+05:30] stopping event stream following graceful shutdown  error="<nil>" module=libcontainerd namespace=moby
failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain DOCKER: iptables failed: iptables -t nat -N DOCKER: iptables v1.6.1: can't initialize iptables table `nat': Memory allocation problem
Perhaps iptables or your kernel needs to be upgraded.
 (exit status 3)

Docker Service status is:
systemctl status docker.service

Output:

● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─hosts.conf
   Active: failed (Result: exit-code) since Sun 2019-08-11 12:35:04 IST; 16min ago
     Docs: https://docs.docker.com
  Process: 12473 ExecStart=/usr/bin/dockerd -H unix:// -H tcp://0.0.0.0:2736 (code=exited, status=1/FAILURE)
 Main PID: 12473 (code=exited, status=1/FAILURE)

Aug 11 12:35:04 BlackCat systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Aug 11 12:35:04 BlackCat systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Aug 11 12:35:04 BlackCat systemd[1]: Stopped Docker Application Container Engine.
Aug 11 12:35:04 BlackCat systemd[1]: docker.service: Start request repeated too quickly.
Aug 11 12:35:04 BlackCat systemd[1]: docker.service: Failed with result 'exit-code'.
Aug 11 12:35:04 BlackCat systemd[1]: Failed to start Docker Application Container Engine.

Docker version:

Client: Docker Engine - Community
 Version:           19.03.1
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        74b1e89
 Built:             Thu Jul 25 21:21:22 2019
 OS/Arch:           linux/amd64
 Experimental:      false
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.40/version: dial unix /var/run/docker.sock: connect: permission denied

System info:

Distributor ID: Ubuntu
Description:    Ubuntu 19.04
Release:        19.04
Codename:       disco
Linux kernel version : 5.1.7

Most helpful comment

What does sudo dockerd say? In my case:

Error starting daemon: Error initializing network controller: Error creating default "bridge" network: could not find an available, non-overlapping IPv6 address pool among the defaults to assign to the network

All 3 comments

I met the same problem just because that I misconfigured the docker.service in a conf file, by passing a param to docker that it can't recognize.
for detial, I write -<parm_name>=<param_value> which should be --<param_name>=<param_value> (lost a leading hypen).

though the true problem is naive, but I hadn't found that until I use journalctl -u docker.service to check the detail log. At the first sight, the output docker.service: Start request repeated too quickly. of systemctl status docker.service may misguide us.

docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-12-31 03:10:03 IST; 1min 39s ago
Docs: https://docs.docker.com
Process: 10087 ExecStart=/usr/bin/docker daemon -H fd:// (code=exited, status=1/FAILURE)
Main PID: 10087 (code=exited, status=1/FAILURE)

Dec 31 03:10:03 NAP-CE-LAP-033 systemd[1]: Starting Docker Application Container Engine...
Dec 31 03:10:03 NAP-CE-LAP-033 docker[10087]: unable to configure the Docker daemon with file /etc/docker/d
Dec 31 03:10:03 NAP-CE-LAP-033 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILU
Dec 31 03:10:03 NAP-CE-LAP-033 systemd[1]: docker.service: Failed with result 'exit-code'.
Dec 31 03:10:03 NAP-CE-LAP-033 systemd[1]: Failed to start Docker Application Container Engine.

What does sudo dockerd say? In my case:

Error starting daemon: Error initializing network controller: Error creating default "bridge" network: could not find an available, non-overlapping IPv6 address pool among the defaults to assign to the network

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Ingosmar89219 picture Ingosmar89219  ·  3Comments

bryanhuntesl picture bryanhuntesl  ·  3Comments

rcdailey picture rcdailey  ·  3Comments

dnephin picture dnephin  ·  3Comments

dedalusj picture dedalusj  ·  3Comments