Creating config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
Synchronizing state of unattended-upgrades.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable unattended-upgrades
Processing triggers for libc-bin (2.23-0ubuntu10) ...
Processing triggers for systemd (229-4ubuntu21.9) ...
gpg: keyring `/tmp/tmpa7ktcm9q/secring.gpg' created
gpg: keyring `/tmp/tmpa7ktcm9q/pubring.gpg' created
gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpa7ktcm9q/trustdb.gpg: trustdb created
gpg: key E5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Surā" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
'ascii' codec can't decode byte 0xc5 in position 92: ordinal not in range(128)UPDATE: I managed to fix this by running these commands:
sudo locale-gen en_US.UTF-8
export LANG=en_US.UTF-8
Now when I try to reinstall ee4 new error showed up:
4700K .......... .......... .......... .......... .......... 90% 58.0M 0s
4750K .......... .......... .......... .......... .......... 91% 65.9M 0s
4800K .......... .......... .......... .......... .......... 92% 62.2M 0s
4850K .......... .......... .......... .......... .......... 93% 62.4M 0s
4900K .......... .......... .......... .......... .......... 94% 51.0M 0s
4950K .......... .......... .......... .......... .......... 95% 64.8M 0s
5000K .......... .......... .......... .......... .......... 96% 63.3M 0s
5050K .......... .......... .......... .......... .......... 97% 74.8M 0s
5100K .......... .......... .......... .......... .......... 98% 63.6M 0s
5150K .......... .......... .......... .......... .......... 99% 71.2M 0s
5200K .......... .......... .......... .......... ... 100% 77.7M=0.1s
2018-11-22 13:27:25 (36.8 MB/s) - ā/usr/local/bin/eeā saved [5369193/5369193]
Error: docker not installed or not running.
Can you be able to help me fix this issue? Thank you!
Iām installing ee4 on a OpenVZ VPS with Ubuntu 16.04 OS.
@seyntjim Can you check if docker is installed?
Please share the output of following commands:
docker version
service docker status
DOCKER VERSION
Client: Version: 18.09.0 API version: 1.39 Go version: go1.10.4 Git commit: 4d60db4 Built: Wed Nov 7 00:48:57 2018 OS/Arch: linux/amd64 Experimental: false Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
SERVICE DOCKER STATUS:
ā docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: e
Active: inactive (dead) since Thu 2018-11-22 13:27:35 EST; 25min ago
Docs: https://docs.docker.com
Process: 13189 ExecStart=/usr/bin/dockerd -H unix:// (code=killed, signal=TERM
Main PID: 13189 (code=killed, signal=TERM)
Nov 22 13:27:35 depeds systemd[1]: Starting Docker Application Container Engine.
Nov 22 13:27:35 depeds systemd[1]: Dependency failed for Docker Application Cont
Nov 22 13:27:35 depeds systemd[1]: docker.service: Job docker.service/start fail
Nov 22 13:27:35 depeds systemd[1]: Stopped Docker Application Container Engine.I tried to start docker and it hereās the output:
A dependency job for docker.service failed. See ājournalctl -xeā for details.
I tried running journalctl -xe command and here's the error:
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Nov 22 13:54:31 depeds systemd[1]: Starting containerd container runtime...
-- Subject: Unit containerd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit containerd.service has begun starting up.
Nov 22 13:54:31 depeds modprobe[15771]: modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file
Nov 22 13:54:31 depeds modprobe[15771]: modprobe: FATAL: Module overlay not found in directory /lib/modules/2.6.32-042stab134.3
Nov 22 13:54:31 depeds systemd[1]: containerd.service: Control process exited, code=exited status=1
Nov 22 13:54:31 depeds systemd[1]: Failed to start containerd container runtime.
-- Subject: Unit containerd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit containerd.service has failed.
--
-- The result is failed.
Nov 22 13:54:31 depeds systemd[1]: Dependency failed for Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is dependency.
Nov 22 13:54:31 depeds systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
Nov 22 13:54:31 depeds systemd[1]: containerd.service: Unit entered failed state.
Nov 22 13:54:31 depeds systemd[1]: containerd.service: Failed with result 'exit-code'.
Nov 22 13:54:31 depeds systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has finished shutting down.
lines 1834-1870/1870 (END)I have same problem. I installed EE4 on Ubuntu 18.04 LTS as a LXC with Proxmox.
Quite likely your host doesnāt support Docker, just like lots of mine.
Only solution Iāve found is to run EasyEngine 3
Unfortunately, we canāt help unless you get Docker running. Thatās the whole point of Docker abstraction. You ensure, you have Docker up and running, we will take care of the rest! 
It appears that you guys are using OpenVZ 6, as per this thread, https://stackoverflow.com/a/35951482
I think you may ask your hosting company to use upgrade Kernal and/or OpenVZ. Or in general, ask them to help you run Docker.
You may also change the hosting company. EasyEngine v4 is confirmed to run on DigitalOcean, Linode, Vultr, Amazon, Google Cloud, and Azure. There are too many hosting companies which supports Docker.
If you want to stick with your current hosting company, where Docker is not supported, then you may stick to v3. In this case, you may join forces with folks at https://wordops.org/ who are working on v3 fork.
Sorry but the core EE team wonāt be able to look into this further.
1 Like
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.