Device "docker0" does not exist

I’m seeing this on my current install…

# ./launcher rebuild app
Device "docker0" does not exist.

# docker --version
Docker version 1.12.3, build 6b644ec

# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS
Release:	14.04
Codename:	trusty

# uname -a
Linux community 3.13.0-85-generic #129-Ubuntu SMP Thu Mar 17 20:50:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

This is a Digital Ocean 2GB vm… Problems started after applying gnerI suspect I have an incompatible kernel selected.

I’ve gone back to Ubuntu 14.04 x64 vmlinuz-3.13.0-71-generic removed docker-engine and re-installed, but still have the same issue.

This is what’s in my /var/discourse folder. I don’t know what’s up with that docker -> docker entry… maybe that’s old news from a long time ago?

:/var/discourse# ls -al
total 100
drwxr-xr-x 11 root root  4096 Nov 23 12:11 .
drwxr-xr-x 13 root root  4096 Sep  6  2014 ..
drwxr-xr-x  2 root root  4096 Feb 22  2015 bin
drwxr-xr-x  2 root root  4096 Nov  1 10:14 cids
drwxr-xr-x  2 root root  4096 Oct 20 23:30 containers
-rwxr-xr-x  1 root root 13303 Nov  1 09:46 discourse-setup
lrwxrwxrwx  1 root root     6 Sep  6  2014 docker -> docker
drwxr-xr-x  8 root root  4096 Nov 23 12:35 .git
-rw-r--r--  1 root root   290 Nov  1 09:46 .gitignore
drwxr-xr-x  9 root root  4096 Nov 23 12:11 image
-rwxr-xr-x  1 root root 19151 Nov 23 12:11 launcher
-rw-r--r--  1 root root  8281 Nov  1 09:46
drwxr-xr-x  2 root root  4096 Sep 13 12:20 samples
drwxr-xr-x  2 root root  4096 Apr 23  2016 scripts
drwxr-xr-x  4 root root  4096 Aug 28 19:47 shared
drwxr-xr-x  3 root root  4096 Nov 23 12:11 templates
-rw-r--r--  1 root root     0 May 28 00:34 v1.0.0
-rw-r--r--  1 root root     0 May 28 00:34 v1.0.1
-rw-r--r--  1 root root  1122 Nov  6  2015 Vagrantfile

What else might get me past the failure to find docker here?

Did you try to reboot the server?


Yes, sorry for not stating that. Each time I tried a new kernel, after reinstalling docker, and once more before posting.

1 Like

What about manually starting the docker service?

1 Like
# service docker start
start: Job is already running: docker

Does ifconfig show the docker0 entry?

It does not

# ifconfig 
eth0      Link encap:Ethernet  HWaddr 04:01:1a:XX:XX:XX  
          inet addr:107.170.XX.XX  Bcast:107.170.XXX.255  Mask:
          inet6 addr: fe80::601:XXXXXX:XXXXX:XXXXX/64 Scope:Link
          RX packets:2059 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1903 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:274024 (274.0 KB)  TX bytes:225541 (225.5 KB)

lo        Link encap:Local Loopback  
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:288 errors:0 dropped:0 overruns:0 frame:0
          TX packets:288 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:20667 (20.6 KB)  TX bytes:20667 (20.6 KB)

So it claims docker is running, however no docker network interface in sight?

You can try to debug this, restarting over with a backup in a new droplet may be faster.

1 Like

True story! Would the kernel change prevent that from showing up?

Your comments led me to a solution, related to changing the kernel, and not having the right supporting packages installed


apt-get install linux-image-extra-$(uname -r)
This works for me.

My container is rebuilding now. :heart:

1 Like

It can be anything.

If you are felling adventurous you can try to track it down with less /var/log/upstart/docker.log.

1 Like

Not in my case.

I’m also getting the same error message on trying to bootstrap discourse.

Docker installation failed on “unable to locate docker-engine”.

Then I’ve tried a second way by using apt-get install docker-engine. Result is the same. Can’t be found.

I’m running Ubuntu 16.10 minimal (at Hetzner Germany).

Any clue how to fix it?

Hi everyone,

I got the same error message Device "docker0" does not exist after i got disconnected in the middle of an upgrade by running 'do-release-upgrade'. What can I do to get it running again? Much appreciate the help!

Restarting the docker using the following command solved the issue:

./launcher stop app
./launcher start app

Thanks everyone!


this comes only when you are running the installation in a docker instance its not a proper vps server on which you are trying to install - i have faced same issue… check with your provider once

You sir, saved my ass


I was facing the same issue then i checked the space in the server where docker is installed and it was full so removed some files, docker came up.
As there was no space ,docker was not able create network and hence service was down n was not able to start the service also