Arch Linux

_JZA_

Member

Registered: 2014-08-28

Posts: 32

Can't boot docker with systemd after a kernel update

Is there a way I can workaround having to reboot everytime the kernel is updated to be able to run docker with systemd. After a kernel update, even a minor one, my docker service stop working and I need to reboot. If I get somet something like:

sudo systemctl start docker
[sudo] password for jza: 
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Journal logs say:

-- The job identifier is 41722.
feb 12 23:08:09 dellg7 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://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit docker.socket has finished successfully.
-- 
-- The job identifier is 41722.
feb 12 23:08:09 dellg7 systemd[1]: docker.service: Start request repeated too quickly.
feb 12 23:08:09 dellg7 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'.
feb 12 23:08:09 dellg7 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 41618 and the job result is failed.
feb 12 23:08:09 dellg7 systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.