Docker service not able to start anymore because of modprobe error

by Dominik Spiertz   Last Updated November 08, 2018 23:00 PM

I just ran in some issues with my server running docker that I cannot fix myself. Im using Docker version 18.09.0, build 4d60db4 with Ubuntu 16.04.5 LTS. During the day I noticed, that my docker applications are not available, so I checked the service. When trying to start the docker service with service docker start, I get A dependency job for docker.service failed. See 'journalctl -xe' for details. When checking the journalctl, I get the following output:

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.
systemd[1]: Starting containerd container runtime...
    -- Subject: Unit containerd.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit containerd.service has begun starting up.
modprobe[811]: modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file '/lib/modules/4.4.0/modules.builtin.bin'
modprobe[811]: modprobe: FATAL: Module overlay not found in directory /lib/modules/4.4.0
systemd[1]: containerd.service: Control process exited, code=exited status=1
systemd[1]: Failed to start containerd container runtime.
    -- Subject: Unit containerd.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit containerd.service has failed.
    --
    -- The result is failed.
systemd[1]: Dependency failed for 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 dependency.
systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
systemd[1]: containerd.service: Unit entered failed state.
systemd[1]: containerd.service: Failed with result 'exit-code'.
systemd[1]: Stopped Docker Application Container Engine.
    -- Subject: Unit docker.service has finished shutting down
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit docker.service has finished shutting down.

I tried restarting the server multiple times. Everything else on the system is running perfectly (Mail, Backups, Websites).

I have no experience with modprobe or the error in any case, so any detailed help would be appreciated.

Thanks in advance



Related Questions


debian : mount /var as overlayfs at boot

Updated March 03, 2019 16:00 PM



preventing ipmi kernel drivers from loading

Updated July 12, 2017 13:00 PM

Starting docker-compose with systemd on ubuntu 15.04

Updated August 09, 2016 09:00 AM