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.
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).