Docker Community Forums

Share and learn in the Docker community.

Modules not found (Ubuntu 14.04)


(Jpsh) #1

Hey folks,

I followed the installation documentation to install docker on ubuntu 14.04 (https://docs.docker.com/installation/ubuntulinux/)

After installing docker via “curl -sSL https://get.docker.com/ | sh” it won’t run the hello word container:

root@…:~# docker run hello-world
Cannot connect to the Docker daemon. Is ‘docker -d’ running on this host?

Running “docker daemon” or “docker -d” leads to this:

root@…:~# docker daemon
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
ERRO[0000] ‘overlay’ not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
INFO[0000] Option DefaultDriver: bridge
INFO[0000] Option DefaultNetwork: bridge
WARN[0000] Running modprobe bridge nf_nat br_netfilter failed with message: modprobe: ERROR: …/libkmod/libkmod.c:507 kmod_lookup_alias_from_builtin_file() could not open builtin file '/lib/modules/3.13.0-042stab108.2/modules.builtin.bin’
modprobe: WARNING: Module bridge not found.
modprobe: ERROR: …/libkmod/libkmod.c:507 kmod_lookup_alias_from_builtin_file() could not open builtin file '/lib/modules/3.13.0-042stab108.2/modules.builtin.bin’
modprobe: WARNING: Module nf_nat not found.
modprobe: ERROR: …/libkmod/libkmod.c:507 kmod_lookup_alias_from_builtin_file() could not open builtin file '/lib/modules/3.13.0-042stab108.2/modules.builtin.bin’
modprobe: WARNING: Module br_netfilter not found.
, error: exit status 1
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default “bridge” network: package not installed

What to do?


(Jeff Anderson) #2

Do you have the bridge, nf_nat, and br_netfliter installed and available for your currently running kernel version? It looks like you’re running 3.13.0-042stab108.2, which isn’t the typical ubuntu 14.04 kernel. Do you need to install some kind of extra package to make those modules available for your kernel?


(Ralph Kincade) #3

make sure the updates are run

check kernal version

reboot