After updating the docker to version 18.09.0, I get the following error(Virtual server with Ubuntu 18.04):
Nov 09 20:53:52 localhost.localdomain modprobe[663]: modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open buitin file '/lib/modules/4.15.0/modules.builtin.bin
Nov 09 20:53:52 localhost.localdomain modprobe[663]: modprobe: FATAL: Module overlay not found in directory /lib/modules/4.15.0
uname -a
Linux localhost.localdomain 4.15.0 #1 SMP Wed May 23 10:04:13 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux
Also on LXC container (with Ubuntu 18.04) in Majaro
Nov 09 21:06:38 Ubuntu modprobe[5393]: modprobe: ERROR:
../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.14.78-1-MANJARO/modules.dep.bin'
Nov 09 21:06:38 Ubuntu modprobe[5393]: modprobe: FATAL: Module overlay not found in directory /lib/modules/4.14.78-1-MANJARO
uname -a
Linux Ubuntu 4.14.78-1-MANJARO #1 SMP PREEMPT Sun Oct 21 07:57:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
docker -v
Docker version 18.09.0, build 4d60db4
How can i fix it?
You have to override a portion of the containerd service file:
systemctl edit containerd.service
Then insert the following and save it:
[Service]
ExecStartPre=
After that you'll be able to get docker to start.
For reference: https://github.com/docker/for-linux/issues/475#issuecomment-437373774
Essentially your systemd file needs to have the ExecStartPre value cleared, best to use an override file so an upgrade will properly update the main file.
Related
I'm trying to make an OpenVPN server using docker I just started creating a tunnel between 2 containers after installing openvpn on both container the command :
openvpn --dev tun1 --ifconfig 10.0.0.1 10.0.0.2
gave me this error:
Mon Jul 12 12:26:28 2021 disabling NCP mode (--ncp-disable) because not in P2MP client or server mode
Mon Jul 12 12:26:28 2021 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 27 2021
Mon Jul 12 12:26:28 2021 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10
Mon Jul 12 12:26:28 2021 ******* WARNING *******: All encryption and authentication features disabled -- All data will be tunnelled as clear text and will not be protected against man-in-the-middle changes. PLEASE DO RECONSIDER THIS CONFIGURATION!
Mon Jul 12 12:26:28 2021 ERROR: Cannot open TUN/TAP dev /dev/net/tun: No such file or directory (errno=2)
Mon Jul 12 12:26:28 2021 Exiting due to fatal error
is the problem related to working on a container?
is it fine to make a OpenVPN server on a ubuntu image-based container?
if there is any other tips to make an OpenVPN server please tell me I'm new in this topic.
I tried to install the docker in CentOS 7 and got daemon error. I tried all the methods available on the internet for installation and for debugging but none really worked! I even tried to install older versions of docker that didn't work either.
SELinux is Disabled.
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
docker version
Client:
Version: 1.13.1
API version: 1.26
Package version:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
systemctl status docker.service -l
Redirecting to /bin/systemctl status -l docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2020-04-10 18:00:02 CEST; 49min ago
Docs: http://docs.docker.com
Process: 4510 ExecStart=/usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --init-path=/usr/libexec/docker/docker-init-current --seccomp-profile=/etc/docker/seccomp.json $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY $REGISTRIES (code=exited, status=1/FAILURE)
Main PID: 4510 (code=exited, status=1/FAILURE)
Apr 10 18:00:01 ns3138286 systemd[1]: Starting Docker Application Container Engine...
Apr 10 18:00:01 ns3138286 dockerd-current[4510]: time="2020-04-10T18:00:01.506877169+02:00" level=info msg="libcontainerd: new containerd process, pid: 4522"
Apr 10 18:00:02 ns3138286 dockerd-current[4510]: time="2020-04-10T18:00:02.514107274+02:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded."
Apr 10 18:00:02 ns3138286 dockerd-current[4510]: Error starting daemon: error initializing graphdriver: driver not supported
Apr 10 18:00:02 ns3138286 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Apr 10 18:00:02 ns3138286 systemd[1]: Failed to start Docker Application Container Engine.
Apr 10 18:00:02 ns3138286 systemd[1]: Unit docker.service entered failed state.
Apr 10 18:00:02 ns3138286 systemd[1]: docker.service failed.
Difficult to provide an exact solution to this question without more details, however, the error message is clear:
'overlay' not found as a supported filesystem on this host
Please note:
To configure Docker to use the overlay storage driver your Docker host must be running version 3.18 of the Linux kernel (preferably
newer) with the overlay kernel module loaded.
Check the kernel version with uname -r
If you have installed a new kernel since installing docker, try rebooting your machine.
If you do not explicitly need overlay, you can also specify storage drivers in the /etc/docker/daemon.json file - 'devicemapper' was the preferred storage driver for kernels that do not support overlay.
Docker is not able to start containers anymore because docker-containerd-shim executable was no found in $PATH.
The thing is that docker-containerd-shim executable is not found anywhere on the machine while there is another executable with almost the same name: "containerd-shim" under /usr/bin directory.
I restarted the service and everything is back to normal. Does creating symbolic link "docker-containerd-shim" ---> "container-shim" could solve the problem?
Docker version: 18.09.7
OS: Ubuntu 16.04 LTS
We had a similar error in our Jenkins pipeline.
Reinstalling docker with a stable channel fixed it.
$ sudo add-apt-repository \
"deb [arch=amd64] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) \
stable"
(https://docs.docker.com/install/linux/docker-ce/ubuntu/)
So we assume it's a nightly / test build problem.
(don't remember which channel we had before)
This happened to me on an Google Compute Engine. The VM runs an gitlab-runner for CI purpose.
It seems like the nigly upgrade, which is enabled for this image ubuntu-1804-bionic-v20180723 caused a restart which lead to this misbehaviour.
[...]
Jul 9 06:30:59 gitlab-runner systemd[1]: Starting Daily apt upgrade and clean activities...
Jul 9 06:31:22 gitlab-runner systemd[1]: Reloading.
Jul 9 06:31:23 gitlab-runner systemd[1]: Stopping LSB: automatic crash report generation...
Jul 9 06:31:23 gitlab-runner apport[21840]: * Stopping automatic crash report generation: apport
Jul 9 06:31:23 gitlab-runner apport[21840]: ...done.
Jul 9 06:31:23 gitlab-runner systemd[1]: Stopped LSB: automatic crash report generation.
Jul 9 06:31:23 gitlab-runner systemd[1]: Reloading.
Jul 9 06:31:24 gitlab-runner systemd[1]: message repeated 5 times: [ Reloading.]
Jul 9 06:31:25 gitlab-runner systemd[1]: Starting LSB: automatic crash report generation...
Jul 9 06:31:25 gitlab-runner apport[22110]: * Starting automatic crash report generation: apport
Jul 9 06:31:25 gitlab-runner apport[22110]: ...done.
Jul 9 06:31:25 gitlab-runner systemd[1]: Started LSB: automatic crash report generation.
Jul 9 06:31:32 gitlab-runner systemd[1]: Reloading.
Jul 9 06:31:33 gitlab-runner systemd[1]: docker.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Jul 9 06:31:36 gitlab-runner systemd[1]: Reloading.
Jul 9 06:31:36 gitlab-runner systemd[1]: Reloading.
Jul 9 06:31:36 gitlab-runner systemd[1]: Starting containerd container runtime...
Jul 9 06:31:36 gitlab-runner systemd[1]: Started containerd container runtime.
Jul 9 06:31:36 gitlab-runner systemd[1]: Reloading.
[...]
Indeed, rebooting fixed this issue.
Suddently my docker daemon stop and never turned on again. I'm running docker on a Linux raspberrypi 4.1.13-v7+. It worked before until last week when my docker service suddenly stop working and I don't have a clue why.
My docker version is:
raspberrypi:~ $ docker version
Client:
Version: 1.10.3
API version: 1.22
Go version: go1.4.3
Git commit: 20f81dd
Built: Thu Mar 10 22:23:48 2016
OS/Arch: linux/arm
An error occurred trying to connect: Get http:///var/run/docker.sock/v1.22/version: read unix /var/run/docker.sock: connection reset by peer
Socket is ok:
● docker.socket - Docker Socket for the API
Loaded: loaded (/lib/systemd/system/docker.socket; disabled)
Active: active (listening) since Sat 2018-03-17 00:42:46 UTC; 6s ago
Listen: /var/run/docker.sock (Stream)
Looking to my service status you can see the following log:
docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled)
Active: failed (Result: start-limit) since Sat 2018-03-17 00:05:52 UTC; 4min 55s ago
Docs: https://docs.docker.com
Process: 2891 ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE)
Main PID: 2891 (code=exited, status=1/FAILURE)
Mar 17 00:05:52 raspberrypi docker[2891]: time="2018-03-17T00:05:52.743474604Z" level=debug msg="ReleaseAddress(LocalDefault/172.17.0.0/16, 172.17.0.1)"
Mar 17 00:05:52 raspberrypi docker[2891]: time="2018-03-17T00:05:52.758090386Z" level=debug msg="ReleasePool(LocalDefault/172.17.0.0/16)"
Mar 17 00:05:52 raspberrypi docker[2891]: time="2018-03-17T00:05:52.772819345Z" level=debug msg="Cleaning up old shm/mqueue mounts: start."
Mar 17 00:05:52 raspberrypi docker[2891]: time="2018-03-17T00:05:52.773269239Z" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: package not installed"
Mar 17 00:05:52 raspberrypi systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Mar 17 00:05:52 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
I already tried this solution but for me it didn't work.
How can I make my docker service start again? It seems that a package is not installed but I tried to:
raspberrypi:~ $ modprobe bridge
modprobe: FATAL: Module bridge not found.
I have just installed docker on a fedora 18 system:
Linux draco 3.8.4-202.fc18.x86_64 #1 SMP Thu Mar 21 17:02:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[mike#draco docker-master]$ sudo ./docker run -i -t base /bin/bash
2013/04/02 08:24:59 net: no such interface
Can anyone tell me what is missing here? lxc is installed, as well as lxc-libs, and lxc-templates.
You need a network bridge configured with the name lxcbr0.
To do this, you can run (as root):
brctl addbr lxcbr0
ifconfig lxcbr0 10.65.41.1
That usually means you don't have aufs setup correctly.
See https://github.com/dotcloud/docker/issues/183 for more information.