Share and learn in the Docker community.
The power in the building went down and the server was unexpectedly restarted.
After that, the server’s docker daemon runs, but all of the docker’s commands do not run.
Check the docker status as follows.
I checked the server’s resources and found that there are enough resources.
The system OS is CentOS 7.
Git-lab is a spinning docker, so the data in the docker should not fly away.
Please help. I haven’t been able to work properly for 3 days because I haven’t been a docker.
Thank you!
Please, use </> button to share codes, terminal outputs, error messages instead of sharing screenshots. That helps others to search for similar issues and us to read it more easily and quote parts of the message so we can help you more quickly. You can find a complete guide in the following post: How to format your forum posts
The only supported CentOS at this moment is CentOS 9 stream. You probably have an older Docker version as well. And the error message indicates you are using a loopback device for Docker storage. It also mentions devicemapper which is deprecated
Use a supported Docker version with supported storage driver and there is a better chance it will work after shutting down and rebooting the machine.
Thank you. I’ll apply it.
You mean your containers are not automatically restarted? Was that mode set during initial container start?
Try docker ps -a to check if they are just stopped and you might manually start them.
Although I also highly recommend to upgrade for security and bug fixes.
@bluepuma77 has a good point. I focused only on the warnings in the error message and the “docker commands do not respond” statement in the title, but you need to set the required restart policy. when you create the container. A docker container is not a docker command, so which one is actually the problem?
docker info, docker exec, docker run and other docker commands don’t work