# Device "docker0" does not exist
**URL:** https://meta.discourse.org/t/device-docker0-does-not-exist/30216
**Category:** Self-hosting
**Created:** [June 19, 2015, 4:36pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216 "2015-06-19T16:36:59Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Fabian](https://meta.discourse.org/u/Fabian)
#### Post date: [June 19, 2015, 4:37pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/1 "2015-06-19T16:37:00Z")
I just tried to install discourse on my dedicated ubuntu server. I followed this tutorial: [discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md)
of course I do not have a cloud or anything, but my server. I guess it should work anyways.
I am using the terminal of my mac. Here is the problem. After typing in:
```
./launcher bootstrap app
```
I get an error:
```
Device "docker0" does not exist.
Cannot connect to the docker daemon - verify it is running and you have access
```
What can I do? I thought everything went well until this point. Any ideas?
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [June 19, 2015, 7:16pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/2 "2015-06-19T19:16:35Z")
that means that the doctor install did not work. What happens if you run `docker info `?
---
### Author:  [@Fabian](https://meta.discourse.org/u/Fabian)
#### Post date: [June 20, 2015, 12:01am UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/3 "2015-06-20T00:01:22Z")
Get http:///var/run/docker.sock/v1.19/info: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 20, 2015, 1:46am UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/4 "2015-06-20T01:46:05Z")
Your docker install is failing. You should look into why Docker is failing to install on your OS. This is usually because the OS is not 64 bit, or the kernel is too old, etc.
We recommend Ubuntu Server 14.04 LTS x64.
---
### Author:  [@Ian\_Wright](https://meta.discourse.org/u/Ian_Wright)
#### Post date: [June 20, 2015, 4:25pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/5 "2015-06-20T16:25:01Z")
I’ve got exactly the same problem, and have been following the same tutorial. `docker info` provides the same information that @Fabian has mentioned.
I’m running the suggested build of Ubuntu and can confirm that I’m on a 64bit version of it. I’m not really experienced with Linux but I couldn’t see any anything that looked like an error during the install of docker. The only thing that I’m aware that I did do which was off script was to add myself to the docker group as per the installer suggestions using:
`sudo usermod -aG docker {USERNAME}`
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 20, 2015, 8:43pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/6 "2015-06-20T20:43:07Z")
Are you not logged in as root when you install Docker via
```
wget -qO- https://get.docker.com/ | sh
```
As per the [official install](https://meta.discourse.org/t/142537?silent=true) docs?
---
### Author:  [@Ian\_Wright](https://meta.discourse.org/u/Ian_Wright)
#### Post date: [June 20, 2015, 9:16pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/7 "2015-06-20T21:16:53Z")
Jeff - appreciate you trying to help with this.
So the `wget` command you listed is exactly as I ran it. However looking at the images in the docs (and you referring to root) they’re running under the `root@forum` user. Mine wasn’t run under root (I actually read you can’t access root on Ubuntu [http://askubuntu.com/questions/91598/how-do-i-login-as-root](http://askubuntu.com/questions/91598/how-do-i-login-as-root)) so I’ve been using the admin account I created `ian@Ubuntu` and using `sudo` when hitting permissions errors.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [June 20, 2015, 9:37pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/8 "2015-06-20T21:37:35Z")
It should work if you’re a member of the `docker` group.
---
### Author:  [@Ian\_Wright](https://meta.discourse.org/u/Ian_Wright)
#### Post date: [June 20, 2015, 9:56pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/9 "2015-06-20T21:56:27Z")
Yeah, so I believe I did that with the command I mentioned in post #5
`sudo usermod -aG docker {USERNAME}`
---
### Author:  [@Fabian](https://meta.discourse.org/u/Fabian)
#### Post date: [June 21, 2015, 9:30am UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/10 "2015-06-21T09:30:35Z")
> [@codinghorror](#):
>
> Are you not logged in as root
I really have no idea how you can login as root. I mean I did “ssh [root@mysite.com](mailto:root@mysite.com)” so I guess this should be it. Still not sure why it isn’t working then. ☹ I can’t wait trying discourse out :wat:
by the way, I found out that my kernel is 2.X. so I tried to upgrade it. But it doesnt work either:
> apt-get install linux-image-generic-lts-trusty
> Reading package lists… Done
> Building dependency tree
> Reading state information… Done
> E: Unable to locate package linux-image-generic-lts-trusty
edit: now somehow i got a new kernel 3.18… but i keep getting errors when trying to install docker ☹
---
### Author:  [@Fabian](https://meta.discourse.org/u/Fabian)
#### Post date: [June 22, 2015, 11:33pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/11 "2015-06-22T23:33:16Z")
so what am I supposed to do right now? no chance to install discourse?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [June 22, 2015, 11:46pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/12 "2015-06-22T23:46:04Z")
You need to get docker working on your server first, perhaps submit a support request on [https://forums.docker.com/](https://forums.docker.com/)
---
### Author:  [@Fabian](https://meta.discourse.org/u/Fabian)
#### Post date: [June 27, 2015, 4:14pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/13 "2015-06-27T16:14:51Z")
Unfortunately, they do not reply. No support on their forum. Will there be another way to install discourse in future? Why is it, that you have to install docker etc.? Discourse is the first software with such complicated install I met, so far all I had to do were some simple clicks on install and upload via ftp 😃
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 27, 2015, 7:34pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/14 "2015-06-27T19:34:16Z")
You could install on Digital Ocean, that works well for us.
---
### Author:  [@bitspill](https://meta.discourse.org/u/bitspill)
#### Post date: [July 6, 2015, 9:04am UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/15 "2015-07-06T09:04:52Z")
I’m on Ubuntu 15.04 and had to run `service docker start` to get the docker daemon running and then I could bootstrap without issue.
---
### Author:  [@ottodevs](https://meta.discourse.org/u/ottodevs)
#### Post date: [July 14, 2015, 2:35pm UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/16 "2015-07-14T14:35:46Z")
I faced that error some minutes ago…
After reviewing my actions I discovered that I updated the lxc-docker from 1.5 to 1.7 in the VPS with ubuntu server…
So I did:
apt-get update && apt-get install lxc-docker-1.5
then sudo reboot
That removes the newest lxc-docker, that causes a conflict with the driveimage storage method and prevents the docker daemon to start correctly.
It is for sure not the cleanest solution, but is fast and safe for the moment.
Source:
[https://github.com/docker/docker/issues/14035](https://github.com/docker/docker/issues/14035)
---
### Author:  [@John\_Byrd](https://meta.discourse.org/u/John_Byrd)
#### Post date: [October 1, 2015, 2:13am UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/17 "2015-10-01T02:13:47Z")
In my case, it turned out to be that the docker daemon was not running, and was not started at boot time. Check your OS manual for instructions on how to start this daemon.
---
### Author:  [@A\_Tong\_Vy\_Binh](https://meta.discourse.org/u/A_Tong_Vy_Binh)
#### Post date: [October 16, 2015, 8:38am UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/18 "2015-10-16T08:38:32Z")
Hi. I got same thing as you. I ran ‘service docker start’ and every thing work find then.
---
### Author:  [@A\_Tong\_Vy\_Binh](https://meta.discourse.org/u/A_Tong_Vy_Binh)
#### Post date: [October 16, 2015, 10:02am UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/20 "2015-10-16T10:02:39Z")
I built success but how to develop this source and how to deploy to server?
---
### Author:  [@ghostsf](https://meta.discourse.org/u/ghostsf)
#### Post date: [November 11, 2016, 10:30am UTC](https://meta.discourse.org/t/device-docker0-does-not-exist/30216/21 "2016-11-11T10:30:20Z")
oh yes , u are right .
[Next page](https://meta.discourse.org/t/device-docker0-does-not-exist/30216.md?page=2)