Why does docker service fails to start

I’m currently running tumbleweed with docker 1.13. I’m a bit clueless on why the docker service fails to run. Can anyone point me in the right direction?

– Unit docker.service has begun starting up.
Apr 03 18:01:28 dell-koen docker_service_helper.sh[15210]: Waiting for docker daemon to start
Apr 03 18:01:28 dell-koen dockerd[15209]: time=“2017-04-03T18:01:28.988174266+02:00” level=warning msg=“!] DON’T BIND ON ANY IP ADDRESS WITHOUT setting -tlsverify IF YOU DON’T KNOW WHAT YOU’RE DOING !]”
Apr 03 18:01:28 dell-koen dockerd[15209]: time=“2017-04-03T18:01:28.992578227+02:00” level=info msg=“[graphdriver] using prior storage driver: btrfs”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.013513998+02:00” level=info msg=“Graph migration to content-addressability took 0.00 seconds”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.013744969+02:00” level=warning msg=“Your kernel does not support swap memory limit.”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.013790195+02:00” level=warning msg=“Your kernel does not support cgroup rt period”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.013802883+02:00” level=warning msg=“Your kernel does not support cgroup rt runtime”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.014203156+02:00” level=info msg=“Loading containers: start.”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.018669262+02:00” level=info msg=“Firewalld running: false”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.186428424+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”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.273883220+02:00” level=info msg=“Loading containers: done.”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.283390935+02:00” level=warning msg="failed to retrieve docker-runc version: unknown output format: runc version spec: 1.0.0-rc2-dev
"
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.283512790+02:00” level=warning msg=“failed to retrieve docker-init version”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.283722392+02:00” level=info msg=“Daemon has completed initialization”
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.283768439+02:00” level=info msg=“Docker daemon” commit=78d1802 graphdriver=btrfs version=1.13.0
Apr 03 18:01:29 dell-koen dockerd[15209]: time=“2017-04-03T18:01:29.299763231+02:00” level=info msg=“API listen on ::]:2376”
Apr 03 18:01:42 dell-koen kernel: **SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=44:85:00:47:61:66:54:60:09:a8:69:94:08:00 SRC=192.168.1.35 DST=192.168.1.167 LEN=544 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=36731 DPT=42811 LEN=524 **
Apr 03 18:01:43 dell-koen kernel: **SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=44:85:00:47:61:66:54:60:09:a8:69:94:08:00 SRC=192.168.1.35 DST=192.168.1.167 LEN=544 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=59006 DPT=42811 LEN=524 **
Apr 03 18:01:44 dell-koen kernel: **SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=44:85:00:47:61:66:54:60:09:a8:69:94:08:00 SRC=192.168.1.35 DST=192.168.1.167 LEN=544 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=34631 DPT=42811 LEN=524 **
Apr 03 18:01:45 dell-koen kernel: **SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=44:85:00:47:61:66:54:60:09:a8:69:94:08:00 SRC=192.168.1.35 DST=192.168.1.167 LEN=544 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=34151 DPT=42811 LEN=524 **
Apr 03 18:01:49 dell-koen kernel: SFW2-INext-DROP-DEFLT IN=wlp2s0 OUT= MAC=33:33:00:00:00:fb:0e:65:c9:78:c3:04:86:dd SRC=fe80:0000:0000:0000:0c65:c9ff:fe78:c304 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=72 TC=0 HOPLIMIT=1 FLOWLBL=0
Apr 03 18:02:29 dell-koen docker_service_helper.sh[15210]: Docker is dead
Apr 03 18:02:29 dell-koen dockerd[15209]: time=“2017-04-03T18:02:29.794539225+02:00” level=info msg=“Processing signal ‘terminated’”
Apr 03 18:02:29 dell-koen systemd[1]: docker.service: Control process exited, code=exited status=1
Apr 03 18:02:29 dell-koen systemd[1]: Failed to start Docker Application Container Engine.

This is the ps command the is running for , maybe a minute or so before it dissapears:

koen@dell-koen ~ $ ps afx | grep docker
 1630 ?        Ssl    0:00 /usr/bin/**docker**d --containerd /run/containerd/containerd.sock --add-runtime oci=/usr/bin/**docker**-runc -H tcp://0.0.0.0:2376
 1632 ?        Ss     0:00 /bin/bash /usr/lib/**docker**/**docker**_service_helper.sh wait
 4510 pts/3    S+     0:00  |       \_ grep --color=auto **docker**


This is the journal after booting the system, could it be network related?


Apr 04 08:46:51 dell-koen systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit docker.service has begun starting up.
Apr 04 08:46:51 dell-koen docker_service_helper.sh[1632]: Waiting for docker daemon to start
Apr 04 08:46:51 dell-koen systemd[1]: Started Permit User Sessions.
-- Subject: Unit systemd-user-sessions.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 








...




Apr 04 08:46:51 dell-koen avahi-daemon[1578]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Apr 04 08:46:51 dell-koen avahi-daemon[1578]: New relevant interface docker0.IPv4 for mDNS.
Apr 04 08:46:51 dell-koen avahi-daemon[1578]: Registering new address record for 172.17.0.1 on docker0.IPv4.
Apr 04 08:46:51 dell-koen kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
Apr 04 08:46:51 dell-koen kernel: Linux video capture interface: v2.00
Apr 04 08:46:51 dell-koen mysql-systemd-helper[1694]: 2017-04-04  8:46:51 140129712851200 [Note] /usr/sbin/mysqld (mysqld 10.1.22-MariaDB) starting as process 1694 ...
Apr 04 08:46:51 dell-koen dockerd[1630]: time="2017-04-04T08:46:51.565619444+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"




...








Apr 04 08:46:51 dell-koen dockerd[1630]: time="2017-04-04T08:46:51.614137799+02:00" level=info msg="Loading containers: done."
Apr 04 08:46:51 dell-koen dockerd[1630]: time="2017-04-04T08:46:51.624187612+02:00" level=warning msg="failed to retrieve docker-runc version: unknown output format: runc version spec: 1.0.0-rc2-dev
"
Apr 04 08:46:51 dell-koen dockerd[1630]: time="2017-04-04T08:46:51.624254732+02:00" level=warning msg="failed to retrieve docker-init version"
Apr 04 08:46:51 dell-koen dockerd[1630]: time="2017-04-04T08:46:51.624407148+02:00" level=info msg="Daemon has completed initialization"
Apr 04 08:46:51 dell-koen dockerd[1630]: time="2017-04-04T08:46:51.624424151+02:00" level=info msg="Docker daemon" commit=78d1802 graphdriver=btrfs version=1.13.0
Apr 04 08:46:51 dell-koen systemd[1]: Received SIGRTMIN+21 from PID 352 (plymouthd).
Apr 04 08:46:51 dell-koen dockerd[1630]: time="2017-04-04T08:46:51.629140209+02:00" level=info msg="API listen on ::]:2376"








...






Apr 04 08:46:52 dell-koen kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Apr 04 08:46:52 dell-koen dbus[1580]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.0839] manager: (docker0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Apr 04 08:46:52 dell-koen systemd[1]: Starting WPA Supplicant daemon...
-- Subject: Unit wpa_supplicant.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit wpa_supplicant.service has begun starting up.
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.0868] keyfile: add connection in-memory (39802f40-8327-4c1d-ba22-c8b47be765b1,"docker0")
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.0875] device (docker0): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.0877] device (docker0): state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.0889] device (docker0): Activation: starting connection 'docker0' (39802f40-8327-4c1d-ba22-c8b47be765b1)
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1031] ModemManager available in the bus
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1041] bluez: use BlueZ version 5
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1050] device (docker0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1054] device (docker0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1056] device (docker0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 04 08:46:52 dell-koen dbus[1580]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Apr 04 08:46:52 dell-koen systemd[1]: Started WPA Supplicant daemon.
-- Subject: Unit wpa_supplicant.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit wpa_supplicant.service has finished starting up.
-- 
-- The start-up result is done.
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1079] device (docker0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1083] device (docker0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1086] device (docker0): state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1087] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1093] device (docker0): Activation: successful, device activated.
Apr 04 08:46:52 dell-koen nm-dispatcher[1639]: req:2 'up' [docker0]: new request (4 scripts)
Apr 04 08:46:52 dell-koen nm-dispatcher[1639]: req:2 'up' [docker0]: start running ordered scripts...
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1102] supplicant: wpa_supplicant running
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1103] device (wlp2s0): supplicant interface state: init -> starting
Apr 04 08:46:52 dell-koen NetworkManager[1607]: <info>  [1491288412.1108] connectivity: check for uri 'http://conncheck.opensuse.org' failed with 'Error resolving “conncheck.opensuse.org”: Name or service not known'

ifconfig


**dell-koen:/home/koen #** ifconfig
docker0   Link encap:Ethernet  HWaddr 02:42:73:55:3E:83   
          inet addr:172.17.0.1  Bcast:0.0.0.0  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0  
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

lo        Link encap:Local Loopback   
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1283 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1283 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000  
          RX bytes:174441 (170.3 Kb)  TX bytes:174441 (170.3 Kb)

wlp2s0    Link encap:Ethernet  HWaddr 44:85:00:47:61:66   
          inet addr:192.168.43.53  Bcast:192.168.43.255  Mask:255.255.255.0
          inet6 addr: fe80::1f3:4029:baf5:b700/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6345 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5160 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000  
          RX bytes:5177149 (4.9 Mb)  TX bytes:1075832 (1.0 Mb)

Created a bugzilla entry for this: https://bugzilla.opensuse.org/show_bug.cgi?id=1032246

I managed to get the daemon running by emptying DOCKER_OPTS in /etc/sysconfig/docker .

Another thing that needed to be changed in that file was DOCKER_OPTS. I had to set that to “-s devicemapper” to avoid some file system errors.

Just installed a brand new TW, and installed docker.

For starters, the docker daemon service itself has no problem… Both in my new install, and likely based on what you posted.
From what you posted, there <may> be a problem related to your container… The question then becomes, “How are you starting up your container?”
To test whether the problem is network related, you should not autostart your container (which may be faulty), you should start manually… And if you’re successful then you can devote your attention to fixing your autostart.

If instead your docker service is unable to start even without autostarting your container, then I recommend you upgrade your TW

zypper dup

And, if you find like I did that yesterday’s TW update won’t work, you may need to re-install TW from scratch (which is what I did).

TSU

So, then the question whether you container now can run?

TSU