Support and News Forum

Hi,
I followed the Cookbook to install bare-metal the pro version. but for some reason the Docker isn't starting up under the right port.
When i re-install i get this error:
apt install --reinstall eve-ng-dockers
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 1,274 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://www.eve-ng.net/repo-bionic bionic/main amd64 eve-ng-dockers amd64 3.0-eve-ng [1,274 B]
Fetched 1,274 B in 0s (23.6 kB/s)
(Reading database ... 141774 files and directories currently installed.)
Preparing to unpack .../eve-ng-dockers_3.0-eve-ng_amd64.deb ...
Unpacking eve-ng-dockers (3.0-eve-ng) over (3.0-eve-ng) ...
Setting up eve-ng-dockers (3.0-eve-ng) ...
Synchronizing state of docker.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable docker
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
mysql: [Warning] Using a password on the command line interface can be insecure.
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?

udo systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-12-29 17:28:22 CET; 4min 24s ago
Docs: https://docs.docker.com
Main PID: 5749 (dockerd)
Tasks: 31
Memory: 43.0M
CPU: 499ms
CGroup: /system.slice/docker.service
└─5749 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.030118719+01:00" level=warning msg="Your kernel does not support swap memory
Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.030148131+01:00" level=warning msg="Your kernel does not support cgroup rt p
Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.030163439+01:00" level=warning msg="Your kernel does not support cgroup rt r
Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.030421071+01:00" level=info msg="Loading containers: start."
Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.170574066+01:00" level=info msg="Default bridge (docker0) is assigned with a
Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.225522938+01:00" level=info msg="Loading containers: done."
Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.292279812+01:00" level=info msg="Docker daemon" commit=afacb8b7f0 graphdrive
Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.292373117+01:00" level=info msg="Daemon has completed initialization"
Dec 29 17:28:22 eve-ng.73networks.com dockerd[5749]: time="2020-12-29T17:28:22.317528791+01:00" level=info msg="API listen on /var/run/docker.sock"
Dec 29 17:28:22 eve-ng.73networks.com systemd[1]: Started Docker Application Container Engine.
lines 1-21/21 (END)


netstat -tln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:444 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6653 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9090 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8005 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4822 0.0.0.0:* LISTEN
tcp6 0 0 :::443 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::21 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::8088 :::* LISTEN


How can i make sure it listen and starts properly ?

I belive i found the solution, not sure why but lets see how it works now:
apt install containerd _> triggered removal etc...
apt install --reinstall eve-ng-dockers --> did a full reinstall including the docker images seen with command "dc images"
Thanx.

exactly you did not install it right at the beginning.
And not do not use subnets: in your lan
172.17.x.x/16
nor 172.29.129.0/24

I'm having this same issue. This is the output I get when trying tin install docker in eve-ng. What am i missing?

root@eve-ng:~# apt install --reinstall eve-ng-dockers
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 5 not upgraded.
Need to get 0 B/1,288 B of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 101177 files and directories currently installed.)
Preparing to unpack .../eve-ng-dockers_4.0-eve-ng_amd64.deb ...
Unpacking eve-ng-dockers (4.0-eve-ng) over (4.0-eve-ng) ...
Setting up eve-ng-dockers (4.0-eve-ng) ...
Synchronizing state of docker.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable docker
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
mysql: [Warning] Using a password on the command line interface can be insecure.
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://127.0.0.1:4243. Is the docker daemon running?

Disregard. I did an update and upgrade on the vm, ran the 'apt install --reinstall eve-ng-dockers' command and and it installed correctly. If someone else is having this issue, i recommend following these steps before you update/upgrade:

https://www.eve-ng.net/index.php/how-to ... t-version/