Let us take closer look at the error docker dead but subsys locked error while starting docker. With the support of our Dokcer hosting support services at Bobcares we will now go through the whole setup process.

Error: docker dead but subsys locked error while starting docker

The docker engine package has been updated. Following that, the user is unable to start the Docker service and receives the “docker dead but subsys locked” while attempting to verify the status of the service.

In normal conditions, the typical answer would be to delete the service’s lock file and dead files. This does not apply in this case.

# rm /var/run/docker/execdriver/native/
# rm /var/lock/subsys/docker
# docker info
The Docker daemon cannot be contacted. Is this server running the docker daemon?
# /etc/init.d/docker status
docker dead but subsys locked
# /etc/init.d/docker start
Starting docker: .......... [FAILED]
# rpm -qa | grep docker
docker-engine-1.10.3-1.0.3.el6.x86_64  <<--- currently installed package
# uname -a
Linux ol65-lxc 4.1.12-37.2.2.el6uek.x86_64 #2 SMP Thu Mar 16 17:04:03 IST 2023 x86_64 x86_64 x86_64 GNU/Linux
# tail -n 10 /var/log/docker
Thu Mar 16 17:04:03 IST 2023
flag provided but not defined: -d
See '/usr/bin/docker --help'.
Thu Mar 16 17:04:03 IST 2023
flag provided but not defined: -d
See '/usr/bin/docker --help'.
Thu Mar 16 17:04:03 IST 2023
flag provided but not defined: -d
See '/usr/bin/docker --help'.
Thu Mar 16 17:04:03 IST 2023

Error: subsys locked error while starting docker: Solution

The docker engine is not compatible with the UEK4 kernel version. The issue can be resolved by downgrading the docker-engine package to a previous version.

The “yum list” command will only display the most recent version available in the channel. The “showduplicates” option can be used to display previous versions, as seen below. Then, as indicated, we can uninstall and reinstall the software.

# yum list --showduplicates | grep -i docker-engine
docker-engine.x86_64 1.10.3-1.0.3.el6 @ol6_addons
docker-engine.x86_64 1.8.2-1.0.2.el6 ol6_addons
docker-engine.x86_64 1.8.3-1.0.1.el6 ol6_addons
docker-engine.x86_64 1.9.1-1.0.1.el6 ol6_addons
docker-engine.x86_64 1.10.3-1.0.1.el6 ol6_addons
docker-engine.x86_64 1.10.3-1.0.2.el6 ol6_addons
docker-engine.x86_64 1.10.3-1.0.3.el6 ol6_addons
# yum remove docker-engine-1.10.3-1.0.3.el6.x86_64 -y
# yum install docker-engine-1.9.1-1.0.1.el6.x86_64 -y

Once completed can successfully start the service. This is the final steps to remove the subsys locked error while starting docker.

# /etc/init.d/docker start
Starting docker: . [ OK ]
# /etc/init.d/docker status
docker (pid 2416) is running...
# docker -d
Warning: '-d' is deprecated, it will be removed soon. See usage.
WARN[0000] please use 'docker daemon' instead.
INFO[0000] [graphdriver] using prior storage driver "btrfs"
INFO[0000] API listen on /var/run/docker.sock
INFO[0000] Firewalld running: false
INFO[0000] Default bridge (docker0) is assigned with an IP address 172.17.0.1/16. Daemon option --bip can be used to set a preferred IP address
INFO[0000] Loading containers: start.
INFO[0000] Loading containers: done.
INFO[0000] Daemon has completed initialization
INFO[0000] Docker daemon commit=08eb66d execdriver=native-0.2 graphdriver=btrfs version=1.9.1

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up, we have now how to remove the error, docker dead but subsys locked error while starting docker. Wuith the surppot of our Docker hosting support services at Bobcares we have seen the whole porcess on how to remove the error.