I followed the instructions in this blog "https://blogs.oracle.com/hlsu/install-docker-on-oracle-linux-7" to install docker engine in my Oracle Linux 7 server.
This is my log for yum install docker-engine :
Loaded plugins: langpacks
ol7_UEKR4 | 1.2 kB 00:00:00
ol7_addons | 1.2 kB 00:00:00
ol7_latest | 1.4 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package docker-engine.x86_64 0:17.06.2.ol-1.0.1.el7 will be installed
--> Processing Dependency: container-selinux >= 2.9 for package: docker-engine-17.06.2.ol-1.0.1.el7.x86_64
--> Running transaction check
---> Package container-selinux.noarch 2:2.21-1.el7 will be installed
--> Processing Dependency: selinux-policy-targeted >= 3.13.1-39 for package: 2:container-selinux-2.21-1.el7.noarch
--> Processing Dependency: selinux-policy-base >= 3.13.1-39 for package: 2:container-selinux-2.21-1.el7.noarch
--> Running transaction check
---> Package selinux-policy-targeted.noarch 0:3.13.1-166.0.3.el7_4.7 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================================================================================
Package Arch Version Repository Size
================================================================================================================================================
Installing:
docker-engine x86_64 17.06.2.ol-1.0.1.el7 ol7_addons 21 M
Installing for dependencies:
container-selinux noarch 2:2.21-1.el7 ol7_addons 28 k
selinux-policy-targeted noarch 3.13.1-166.0.3.el7_4.7 ol7_latest 6.5 M
Transaction Summary
================================================================================================================================================
Install 1 Package (+2 Dependent packages)
Total download size: 27 M
Installed size: 92 M
Is this ok [y/d/N]: y
Downloading packages:
(1/3): container-selinux-2.21-1.el7.noarch.rpm | 28 kB 00:00:00
(2/3): docker-engine-17.06.2.ol-1.0.1.el7.x86_64.rpm | 21 MB 00:00:21
(3/3): selinux-policy-targeted-3.13.1-166.0.3.el7_4.7.noarch.rpm | 6.5 MB 00:00:29
------------------------------------------------------------------------------------------------------------------------------------------------
Total 935 kB/s | 27 MB 00:00:29
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
warning: Failed to open SELinux handle.
Installing : selinux-policy-targeted-3.13.1-166.0.3.el7_4.7.noarch 1/3
Installing : 2:container-selinux-2.21-1.el7.noarch 2/3
Installing : docker-engine-17.06.2.ol-1.0.1.el7.x86_64 3/3
Verifying : docker-engine-17.06.2.ol-1.0.1.el7.x86_64 1/3
Verifying : selinux-policy-targeted-3.13.1-166.0.3.el7_4.7.noarch 2/3
Verifying : 2:container-selinux-2.21-1.el7.noarch 3/3
Installed:
docker-engine.x86_64 0:17.06.2.ol-1.0.1.el7
Dependency Installed:
container-selinux.noarch 2:2.21-1.el7 selinux-policy-targeted.noarch 0:3.13.1-166.0.3.el7_4.7
Complete!
it seems to have installed correctly but the next step i,e. to start the docker gives me this error :
---># systemctl start docker
Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details.
-->#systemctl status docker.service
docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/docker.service.d
└─docker-sysconfig.conf
Active: failed (Result: start-limit) since Thu 2017-12-28 17:48:45 IST; 13s ago
Docs: https://docs.docker.com
Process: 26093 ExecStart=/usr/bin/dockerd $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $INSECURE_REGISTRY (code=exited, status=1/FAILURE)
Main PID: 26093 (code=exited, status=1/FAILURE)
Dec 28 17:48:45 Linuxtest systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Dec 28 17:48:45 Linuxtest systemd[1]: Failed to start Docker Application Container Engine.
Dec 28 17:48:45 Linuxtest systemd[1]: Unit docker.service entered failed state.
Dec 28 17:48:45 Linuxtest systemd[1]: docker.service failed.
Dec 28 17:48:45 Linuxtest systemd[1]: docker.service holdoff time over, scheduling restart.
Dec 28 17:48:45 Linuxtest systemd[1]: start request repeated too quickly for docker.service
Dec 28 17:48:45 Linuxtest systemd[1]: Failed to start Docker Application Container Engine.
Dec 28 17:48:45 Linuxtest systemd[1]: Unit docker.service entered failed state.
Dec 28 17:48:45 Linuxtest systemd[1]: docker.service failed.
-->#journalctl -xe -l -u docker | tail -n 50
[root#Linuxtest ~]# journalctl -xe -l -u docker | tail -n 50
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Dec 29 08:54:39 Linuxtest dockerd[44034]: time="2017-12-29T08:54:39.738769156+05:30" level=info msg="libcontainerd: new containerd process, pid: 44041"
Dec 29 08:54:40 Linuxtest dockerd[44034]: time="2017-12-29T08:54:40.754043731+05:30" level=fatal msg="Your Linux kernel version 3.8.13-55.1.6.el7uek.x86_64 is not supported for running docker. Please upgrade your kernel to 3.10.0 or newer."
Dec 29 08:54:40 Linuxtest systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Dec 29 08:54:40 Linuxtest systemd[1]: Failed to start 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 failed.
Dec 29 08:54:40 Linuxtest systemd[1]: Unit docker.service entered failed state.
Dec 29 08:54:40 Linuxtest systemd[1]: docker.service failed.
Dec 29 08:54:40 Linuxtest systemd[1]: docker.service holdoff time over, scheduling restart.
Dec 29 08:54:40 Linuxtest systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Dec 29 08:54:40 Linuxtest dockerd[44060]: time="2017-12-29T08:54:40.970832804+05:30" level=info msg="libcontainerd: new containerd process, pid: 44063"
Dec 29 08:54:41 Linuxtest dockerd[44060]: time="2017-12-29T08:54:41.978053869+05:30" level=fatal msg="Your Linux kernel version 3.8.13-55.1.6.el7uek.x86_64 is not supported for running docker. Please upgrade your kernel to 3.10.0 or newer."
Dec 29 08:54:41 Linuxtest systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Dec 29 08:54:41 Linuxtest systemd[1]: Failed to start 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 failed.
Dec 29 08:54:41 Linuxtest systemd[1]: Unit docker.service entered failed state.
Dec 29 08:54:41 Linuxtest systemd[1]: docker.service failed.
Dec 29 08:54:42 Linuxtest systemd[1]: docker.service holdoff time over, scheduling restart.
Dec 29 08:54:42 Linuxtest systemd[1]: start request repeated too quickly for docker.service
Dec 29 08:54:42 Linuxtest systemd[1]: Failed to start 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 failed.
Dec 29 08:54:42 Linuxtest systemd[1]: Unit docker.service entered failed state.
Dec 29 08:54:42 Linuxtest systemd[1]: docker.service failed.
Can someone please explain why is this happening?
Thanks a lot!
Please note the error message
Your Linux kernel version 3.8.13-55.1.6.el7uek.x86_64 is not supported for running docker. Please upgrade your kernel to 3.10.0 or newer.
You need kernel 3.10+ to install docker
Related
So I stupidly got a laptop with the latest and greatest hardware, so I had to install ArchLinux (version 5.19.13-arch1-1) instead of debian. I'm only vaguely familiar with linux, my fiance has been helping but this has him stumped too so here we are.
I followed the wiki instructions for installing docker, but consistently get the following error when attempting to start the service:
sudo journalctl --since "5 minutes ago" -xeu docker.service
Oct 26 14:37:34 werk systemd[1]: docker.service: Start request repeated too quickly.
Oct 26 14:37:34 werk systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Oct 26 14:37:34 werk systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 10988 and the job result is failed.
lines 334-369/369 (END)
sudo journalctl --since "5 minutes ago" -ru docker.service
Oct 26 14:37:34 werk systemd[1]: Failed to start Docker Application Container Engine.
Oct 26 14:37:34 werk systemd[1]: docker.service: Failed with result 'exit-code'.
Oct 26 14:37:34 werk systemd[1]: docker.service: Start request repeated too quickly.
Oct 26 14:37:34 werk systemd[1]: Stopped Docker Application Container Engine.
Oct 26 14:37:34 werk systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Oct 26 14:37:34 werk systemd[1]: Failed to start Docker Application Container Engine.
Oct 26 14:37:34 werk systemd[1]: docker.service: Failed with result 'exit-code'.
Oct 26 14:37:34 werk systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Oct 26 14:37:34 werk dockerd[71427]: failed to start daemon: error initializing graphdriver: loopback attach failed
I don't really understand loopback devices, but the result of losetup -f seemed sus:
losetup -f
losetup: cannot find an unused loop device: Permission denied
[me#werk ~]$ sudo losetup -f
losetup: cannot find an unused loop device: No such device
We also theorized that the docker user didn't have sufficient permissions to do what it needed to do, but could not find any user specified in the docker.service file (located at /etc/systemd/system/multi-user.target.wants/docker.service). We tried to run the ExecStart command line specified in the docker.service file as root, but got the following error:
[me#werk ~]$ sudo /usr/bin/dockerd -H fd://
[sudo] password for me:
INFO[2022-10-26T14:56:00.483059782-06:00] Starting up
failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd
So that was a bit of a bust.
To be extra clear, installation was as follows:
pacman -Syu docker
systemctl enable docker.service
systemctl start docker.service
And in case it matters, I'm on a Framework laptop with 12th gen Intel core processors.
I am fairly new to docker and linux and I am having issue installing and running docker. My system config are
Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 5.13.9.rsk.1-amd64
Architecture: x86-64
I followed official instructions. When I run sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin, it had following error
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package docker-compose-plugin
I also tried, sudo systemctl restart docker, which output
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
Then I tried, sudo systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2022-06-10 23:04:17 CST; 1min 41s ago
Docs: https://docs.docker.com
Main PID: 33878 (code=exited, status=1/FAILURE)
CPU: 111ms
Jun 10 23:04:15 6969-69-696 systemd[1]: docker.service: Unit entered failed state.
Jun 10 23:04:15 6969-69-696 systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 10 23:04:17 6969-69-696 systemd[1]: docker.service: Service hold-off time over, scheduling restart.
Jun 10 23:04:17 6969-69-696 systemd[1]: Stopped Docker Application Container Engine.
Jun 10 23:04:17 6969-69-696 systemd[1]: docker.service: Start request repeated too quickly.
Jun 10 23:04:17 6969-69-696 systemd[1]: Failed to start Docker Application Container Engine.
Jun 10 23:04:17 6969-69-696 systemd[1]: docker.service: Unit entered failed state.
Jun 10 23:04:17 6969-69-696 systemd[1]: docker.service: Failed with result 'exit-code'.
journalctl -xe had a very big output which does not seem related to docker (most outputs are Failed to get GPU/HCU type or it is not a GPU/HCU host which would make sense since it is a remote host machine).
I have looked at other similar questions on stackoverflow and those fixes have not worked for me so far. Please let me know if I should be doing something differently or how can I fix it. I really need to get docker running for my work. Any help will be appreciated.
I'm having problems getting docker to run on Manjaro XFCE.
I've installed it with:
sudo pacman -Syu
sudo pacman -S docker
And attempted to run it with:
sudo systemctl start docker.service
But it is failing with this error:
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
and this is the log I get with systemctl status docker.service:
[nimbi#nimbi-manjaro ~]$ systemctl status 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 Thu 2020-10-29 01:31:09 MST; 14min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Process: 14837 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 14837 (code=exited, status=1/FAILURE)
Oct 29 01:31:09 nimbi-manjaro systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Oct 29 01:31:09 nimbi-manjaro systemd[1]: Stopped Docker Application Container Engine.
Oct 29 01:31:09 nimbi-manjaro systemd[1]: docker.service: Start request repeated too quickly.
Oct 29 01:31:09 nimbi-manjaro systemd[1]: docker.service: Failed with result 'exit-code'.
Oct 29 01:31:09 nimbi-manjaro systemd[1]: Failed to start Docker Application Container Engine.
journalctl -xe shows this:
░░ The job identifier is 4697.
Oct 29 01:31:09 nimbi-manjaro systemd[1]: docker.service: Start request repeated too quickly.
Oct 29 01:31:09 nimbi-manjaro systemd[1]: docker.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit docker.service has entered the 'failed' state with result 'exit-code'.
Oct 29 01:31:09 nimbi-manjaro systemd[1]: Failed to start Docker Application Container Engine.
░░ Subject: A start job for unit docker.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit docker.service has finished with a failure.
░░
░░ The job identifier is 4631 and the job result is failed.
Oct 29 01:31:09 nimbi-manjaro systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.
lines 1990-2012/2012 (END)
Attempting to run it manually responds with:
[nimbi#nimbi-manjaro ~]$ /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
INFO[2020-10-29T01:53:00.526035448-07:00] Starting up
dockerd needs to be started with root. To see how to run dockerd in rootless mode with unprivileged user, see the documentation
[nimbi#nimbi-manjaro ~]$ sudo /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
INFO[2020-10-29T01:53:08.550576442-07:00] Starting up
failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd
Anyone know how to fix this?
I've also attempted reinstalling via the AUR package but I get the exact same problem.
I'm on Manjaro XFCE 20.1.2 if it helps.
---EDIT---
I think I figured it out...
I had to use sudo systemctl enable docker.service and then type reboot to let it auto start itself.
It is running now.
Here is my current systemctl status docker.service command output:
[nimbi#nimbi-manjaro ~]$ systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor p>
Active: active (running) since Thu 2020-10-29 02:09:12 MST; 3min 10s ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 946 (dockerd)
Tasks: 15
Memory: 72.9M
CGroup: /system.slice/docker.service
└─946 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/cont>
Oct 29 02:09:10 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:10.29207978>
Oct 29 02:09:10 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:10.29210347>
Oct 29 02:09:10 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:10.36927019>
Oct 29 02:09:11 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:11.20664981>
Oct 29 02:09:11 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:11.50144324>
Oct 29 02:09:11 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:11.96303711>
Oct 29 02:09:11 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:11.96351080>
Oct 29 02:09:11 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:11.97714186>
Oct 29 02:09:12 nimbi-manjaro dockerd[946]: time="2020-10-29T02:09:12.58058471>
Oct 29 02:09:12 nimbi-manjaro systemd[1]: Started Docker Application Container
Docker service running on Centos 7 failed to start, I have some docker images which I want to save at any cost. I have searched a couple of online docs and they all say to delete /var/lib/docker/ dir which I don't want to because all the images and containers stuff is there. Can someone please save me how to get docker back up and running with losing any data.
Log:
[root#BuyPandGDev01 /]# systemctl status docker.service -l
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2018-04-22 00:05:23 UTC; 19min ago
Docs: http://docs.docker.com
Process: 1539 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 $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY $REGISTRIES (code=exited, status=1/FAILURE)
Main PID: 1539 (code=exited, status=1/FAILURE)
Apr 22 00:05:22 BuyPandGDev01 systemd[1]: Starting Docker Application Container Engine...
Apr 22 00:05:22 BuyPandGDev01 dockerd-current[1539]: time="2018-04-22T00:05:22.068920976Z" level=info msg="libcontainerd: new containerd process, pid: 1550"
Apr 22 00:05:23 BuyPandGDev01 dockerd-current[1539]: time="2018-04-22T00:05:23.101036303Z" level=warning msg="devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section."
Apr 22 00:05:23 BuyPandGDev01 dockerd-current[1539]: time="2018-04-22T00:05:23.155223108Z" level=error msg="[graphdriver] prior storage driver \"devicemapper\" failed: devmapper: Base Device UUID and Filesystem verification failed: devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed"
Apr 22 00:05:23 BuyPandGDev01 dockerd-current[1539]: time="2018-04-22T00:05:23.155708413Z" level=fatal msg="Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed"
Apr 22 00:05:23 BuyPandGDev01 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Apr 22 00:05:23 BuyPandGDev01 systemd[1]: Failed to start Docker Application Container Engine.
Apr 22 00:05:23 BuyPandGDev01 systemd[1]: Unit docker.service entered failed state.
Apr 22 00:05:23 BuyPandGDev01 systemd[1]: docker.service failed.
journalctl -xe:
[root#BuyPandGDev01 /]# journalctl -xe
-- Unit docker-storage-setup.service has begun starting up.
Apr 22 00:25:58 BuyPandGDev01 container-storage-setup[2111]: INFO: Volume group backing root filesystem could not be determined
Apr 22 00:25:58 BuyPandGDev01 container-storage-setup[2111]: ERROR: No valid volume group found. Exiting.
Apr 22 00:25:58 BuyPandGDev01 systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=1/FAILURE
Apr 22 00:25:58 BuyPandGDev01 systemd[1]: Failed to start Docker Storage Setup.
-- Subject: Unit docker-storage-setup.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker-storage-setup.service has failed.
--
-- The result is failed.
Apr 22 00:25:58 BuyPandGDev01 systemd[1]: Unit docker-storage-setup.service entered failed state.
Apr 22 00:25:58 BuyPandGDev01 systemd[1]: docker-storage-setup.service failed.
Apr 22 00:25:58 BuyPandGDev01 systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Apr 22 00:25:58 BuyPandGDev01 dockerd-current[2140]: time="2018-04-22T00:25:58.731142431Z" level=info msg="libcontainerd: new containe
Apr 22 00:25:59 BuyPandGDev01 dockerd-current[2140]: time="2018-04-22T00:25:59.767061431Z" level=warning msg="devmapper: Usage of loop
Apr 22 00:25:59 BuyPandGDev01 kernel: device-mapper: table: 253:1: thin: Couldn't open thin internal device
Apr 22 00:25:59 BuyPandGDev01 kernel: device-mapper: ioctl: error adding target to table
Apr 22 00:25:59 BuyPandGDev01 dockerd-current[2140]: time="2018-04-22T00:25:59.835261589Z" level=error msg="[graphdriver] prior storag
Apr 22 00:25:59 BuyPandGDev01 dockerd-current[2140]: time="2018-04-22T00:25:59.835697590Z" level=fatal msg="Error starting daemon: err
Apr 22 00:25:59 BuyPandGDev01 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Apr 22 00:25:59 BuyPandGDev01 systemd[1]: Failed to start 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 failed.
Apr 22 00:25:59 BuyPandGDev01 systemd[1]: Unit docker.service entered failed state.
Apr 22 00:25:59 BuyPandGDev01 systemd[1]: docker.service failed.
Apr 22 00:25:59 BuyPandGDev01 polkitd[703]: Unregistered Authentication Agent for unix-process:2105:147803 (system bus name :1.43, obj
lines 2751-2788/2788 (END)
Any response would be helpful and appreciated.
Thx,
kumar
This error occurred for me when I was upgrading docker. Solution that worked for me was to remove legacy docker files /var/lib/docker/ and restart the docker service. Here is the solution.
# Remove docker files
$ rm -rf /var/lib/docker/
# Restart docker via service or via systemctl
$ service docker restart
$ service docker status
$ systemctl start docker.service
$ systemctl status docker.service
I had this error also starting the docker service:
kernel: device-mapper: table: 253:1: thin: Couldn't open thin internal device
I fixed it by creating a soft link from /var/lib/docker to another location on the machine which had more disk space.
cd /var/lib/
mv docker docker.old
ln -s /path/to/big/disk/docker/ docker
Restart the service:
systemctl restart docker
I installed packstack on my fresh installation of Fedora 21 with all updates. When I run
packstack --allinone I received this error:
ERROR : Error appeared during Puppet run: 192.168. 1.*_keystone.pp Error:
Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone
start'` returned 1: Redirecting to /bin/systemctl start openstack-keystone.service
You will find full trace in log /var/tmp/packstack/20141223-022613-whLvTs/manifests
/192.168.1.*_keystone.pp.log
And this is the log:
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder#services]:
Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder#services]:
Skipping because of failed dependencies
Notice: Finished catalog run in 13.02 seconds
With systemctl status openstack-keystone.service get this:
openstack-keystone.service - OpenStack Identity Service (code-named Keystone)
Loaded: loaded (/usr/lib/systemd/system/openstack-keystone.service; disabled)
Active: failed (Result: start-limit) since Tue 2014-12-23 19:47:36 EET; 1min 59s ago
Process: 22526 ExecStart=/usr/bin/keystone-all (code=exited, status=1/FAILURE)
Main PID: 22526 (code=exited, status=1/FAILURE)
Dec 23 19:47:35 localhost.localdomain systemd[1]: Failed to start OpenStack...
Dec 23 19:47:35 localhost.localdomain systemd[1]: Unit openstack-keystone.s...
Dec 23 19:47:35 localhost.localdomain systemd[1]: openstack-keystone.servic...
Dec 23 19:47:36 localhost.localdomain systemd[1]: start request repeated to...
Dec 23 19:47:36 localhost.localdomain systemd[1]: Failed to start OpenStack...
Dec 23 19:47:36 localhost.localdomain systemd[1]: Unit openstack-keystone.s...
Dec 23 19:47:36 localhost.localdomain systemd[1]: openstack-keystone.servic...
This can happen due SELinux avc denial because of a missing policy.
You can try to put SELinux to permissive mode:
# setenforce 0
A similar bug