My docker engine won’t start anymore. I have been messing with my Debian LXC container and followed instructions here, but I reverted it and now I cannot get my Docker engine to start anymore. Hopefully someone has an idea how to fix this. I’ve restarted the LXC a few times.
Apr 21 11:32:50 docker systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.
Apr 21 11:33:08 docker sudo[2244]: docker : TTY=pts/3 ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/systemctl start docker
Apr 21 11:33:08 docker sudo[2244]: pam_unix(sudo:session): session opened for user root(uid=0) by docker(uid=1000)
Apr 21 11:33:08 docker systemd[1]: Starting Docker Socket for the API.
-- Subject: A start job for unit docker.socket has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit docker.socket has begun execution.
--
-- The job identifier is 1279.
Apr 21 11:33:08 docker systemd[1]: Listening on Docker Socket for the API.
-- Subject: A start job for unit docker.socket has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit docker.socket has finished successfully.
--
-- The job identifier is 1279.
Apr 21 11:33:08 docker systemd[1]: docker.service: Start request repeated too quickly.
Apr 21 11:33:08 docker systemd[1]: docker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit docker.service has entered the 'failed' state with result 'exit-code'.
Apr 21 11:33:08 docker systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: A start job for unit docker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit docker.service has finished with a failure.
--
-- The job identifier is 1278 and the job result is failed.
Apr 21 11:33:08 docker systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.
Apr 21 11:33:08 docker sudo[2244]: pam_unix(sudo:session): session closed for user root
Apr 21 11:33:12 docker sudo[2248]: docker : TTY=pts/3 ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Apr 21 11:33:12 docker sudo[2248]: pam_unix(sudo:session): session opened for user root(uid=0) by docker(uid=1000)
Apr 21 11:35:25 docker sudo[2248]: pam_unix(sudo:session): session closed for user root
Apr 21 11:35:27 docker sudo[2251]: docker : TTY=pts/3 ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Apr 21 11:35:27 docker sudo[2251]: pam_unix(sudo:session): session opened for user root(uid=0) by docker(uid=1000)
Apr 21 11:35:32 docker sudo[2251]: pam_unix(sudo:session): session closed for user root
Apr 21 11:35:40 docker sudo[2256]: docker : TTY=pts/3 ; PWD=/home/docker ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Apr 21 11:35:40 docker sudo[2256]: pam_unix(sudo:session): session opened for user root(uid=0) by docker(uid=1000)