| 1 |
I am using Gentoo as Host OS for Docker containers. I have compiled |
| 2 |
kernel using instructions on page |
| 3 |
https://wiki.gentoo.org/wiki/Docker#Kernel and I have installed Docker |
| 4 |
from Gentoo repository. |
| 5 |
|
| 6 |
Host system informations: |
| 7 |
|
| 8 |
pecan@tux ~ $ uname -a |
| 9 |
Linux tux 4.12.12-gentoo #8 SMP Sat Oct 7 13:58:47 CEST 2017 x86_64 |
| 10 |
Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz GenuineIntel GNU/Linux |
| 11 |
|
| 12 |
Docker version: |
| 13 |
|
| 14 |
pecan@tux ~ $ docker version |
| 15 |
Client: |
| 16 |
Version: 17.03.2-ce |
| 17 |
API version: 1.27 |
| 18 |
Go version: go1.9.1 |
| 19 |
Git commit: f5ec1e2 |
| 20 |
Built: Sat Oct 7 14:50:59 2017 |
| 21 |
OS/Arch: linux/amd64 |
| 22 |
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. |
| 23 |
Is the docker daemon running? |
| 24 |
|
| 25 |
Look at "Cannot connect to the Docker daemon at |
| 26 |
unix:///var/run/docker.sock. Is the docker daemon running?". The same |
| 27 |
message appears if I try get docker system-wide informations: |
| 28 |
|
| 29 |
pecan@tux ~ $ docker info |
| 30 |
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. |
| 31 |
Is the docker daemon running? |
| 32 |
|
| 33 |
The same error appears if I try run the same command as sudo, so this |
| 34 |
error applies to daemon. I tried to check if there a mistake in Docker |
| 35 |
daemon privileges. |
| 36 |
|
| 37 |
pecan@tux ~ $ sudo docker info |
| 38 |
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. |
| 39 |
Is the docker daemon running? |
| 40 |
|
| 41 |
Based on the message I am able to say that maybe Docker daemon not |
| 42 |
running. I checked daemon status to make sure: |
| 43 |
|
| 44 |
pecan@tux ~ $ sudo service docker status |
| 45 |
* status: crashed |
| 46 |
|
| 47 |
Docker daemon is crashed. To see the reason, I looked at the logs: |
| 48 |
|
| 49 |
pecan@tux ~ $ cat /var/log/docker.log |
| 50 |
time="2017-10-07T14:52:13.178261811+02:00" level=info |
| 51 |
msg="libcontainerd: new containerd process, pid: 32311" |
| 52 |
time="2017-10-07T14:52:14.434232306+02:00" level=info msg="Graph |
| 53 |
migration to content-addressability took 0.00 seconds" |
| 54 |
time="2017-10-07T14:52:14.434413425+02:00" level=warning msg="Your |
| 55 |
kernel does not support cgroup blkio weight" |
| 56 |
time="2017-10-07T14:52:14.434423960+02:00" level=warning msg="Your |
| 57 |
kernel does not support cgroup blkio weight_device" |
| 58 |
time="2017-10-07T14:52:14.434759986+02:00" level=info msg="Loading |
| 59 |
containers: start." |
| 60 |
time="2017-10-07T14:52:14.437180876+02:00" level=info msg="Firewalld |
| 61 |
running: false" |
| 62 |
Error starting daemon: Error initializing network controller: list |
| 63 |
bridge addresses failed: no available network |
| 64 |
|
| 65 |
Currently, that is a point in that I do not know what should I do to be |
| 66 |
able run Docker daemon. |
| 67 |
|
| 68 |
Useful informations: |
| 69 |
|
| 70 |
- I am connected to OpenVPN through UDP. |
| 71 |
- I have disabled iptables and ip6tables. |
| 72 |
- I have set 8.8.8.8 and 8.8.4.4 DNS providers. |
| 73 |
- I have running privoxy and tor daemons. |
| 74 |
- I use OpenRC init system. |
| 75 |
|
| 76 |
Can you help me? |
Archives