Jump to content

Recommended Posts

Posted

Hi, I'm Glego and this is my first post.

 

I was just fiddling around with my old BananaPI M1 and M1+, and stumbled upon ARMbian, which has great appraisals on the Bananapi forum.  I'm creating a cluster of various SBC's and thought ARMbian is the OS to go.  Unfortunatly I had an issue when setting up Docker and wanted to share the resolution for future reference. However I couldn't find the root cause, so if any expert would be able to comment on why this is happening, I will be happy the do the tests again.

 

Cheers,
Glego

 

Issue

After installing docker-ce, the service is not starting: docker.service start request repeated too quickly, refusing to start.  When manually starting the docker daemon it mentioned: 'overlay' not found as a supported filesystem on this host. 

 

I've resolved the issue by restarting the host, but I wonder why this issue occurred in the first place...

 

Docker installation

root@bpi2:~# apt-get install docker-ce
Reading package lists... Done
Building dependency tree
Reading state information... Done
docker-ce is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up docker-ce (17.09.0~ce-0~debian) ...
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@bpi2:~# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled)
   Active: failed (Result: start-limit) since Mon 2017-10-16 22:56:46 CEST; 19s ago
     Docs: https://docs.docker.com
  Process: 12988 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE)
 Main PID: 12988 (code=exited, status=1/FAILURE)

Oct 16 22:56:46 bpi2 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Oct 16 22:56:46 bpi2 systemd[1]: Failed to start Docker Application Container Engine.
Oct 16 22:56:46 bpi2 systemd[1]: Unit docker.service entered failed state.
Oct 16 22:56:46 bpi2 systemd[1]: docker.service holdoff time over, scheduling restart.
Oct 16 22:56:46 bpi2 systemd[1]: Stopping Docker Application Container Engine...
Oct 16 22:56:46 bpi2 systemd[1]: Starting Docker Application Container Engine...
Oct 16 22:56:46 bpi2 systemd[1]: docker.service start request repeated too quickly, refusing to start.
Oct 16 22:56:46 bpi2 systemd[1]: Failed to start Docker Application Container Engine.
Oct 16 22:56:46 bpi2 systemd[1]: Unit docker.service entered failed state.

 

Docker Daemon


root@bpi2:/var/lib# dockerd
INFO[2017-10-16T23:14:11.797779579+02:00] libcontainerd: new containerd process, pid: 14950
ERRO[2017-10-16T23:14:12.850973636+02:00] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
ERRO[2017-10-16T23:14:12.874193322+02:00] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded.
INFO[2017-10-16T23:14:12.917922290+02:00] Graph migration to content-addressability took 0.00 seconds
INFO[2017-10-16T23:14:12.925184043+02:00] Loading containers: start.
WARN[2017-10-16T23:14:12.938031260+02:00] Running modprobe bridge br_netfilter failed with message: modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.11.5-sunxi/modules.dep.bin'
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.11.5-sunxi/modules.dep.bin'
, error: exit status 1
WARN[2017-10-16T23:14:12.949860113+02:00] Running modprobe nf_nat failed with message: `modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.11.5-sunxi/modules.dep.bin'`, error: exit status 1
WARN[2017-10-16T23:14:12.961439978+02:00] Running modprobe xt_conntrack failed with message: `modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.11.5-sunxi/modules.dep.bin'`, error: exit status 1
Error starting daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain: iptables failed: iptables -t nat -N DOCKER: modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not open moddep file '/lib/modules/4.11.5-sunxi/modules.dep.bin'
iptables v1.4.21: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
 (exit status 3)

 

ARMbian Version

root@bpi2:/var/lib# cat /etc/armbian.txt
--------------------------------------------------------------------------------
Title:                  Armbian 5.31 Bananapi Debian jessie next
Kernel:                 Linux 4.11.5
Build date:             15.06.2017
Authors:                http://www.armbian.com/authors
Sources:                http://github.com/igorpecovnik/lib
Support:                http://forum.armbian.com/
Changelog:              http://www.armbian.com/logbook/
Documantation:          http://docs.armbian.com/
--------------------------------------------------------------------------------

 

Posted
26 minutes ago, martinayotte said:

Is this file "/lib/modules/4.11.5-sunxi/modules.dep.bin" actually present  ?

 

Good point, it isn't present, I wonder why I didn't spot this...

 

I've upgraded the system before installing docker...

 

root@bpi2:~# ls /lib/modules
4.11.6-sunxi

 

So checking the apt log, I remember there was an issue with the Bluetooth module but further no issues. 

 


Start-Date: 2017-10-16  22:39:09
Commandline: apt-get upgrade -y
Upgrade: perl-modules:armhf (5.20.2-3+deb8u7, 5.20.2-3+deb8u9), libirs-export91:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), perl:armhf (5.20.2-3+deb8u7, 5.20.2-3+deb8u9), libpam-modules-bin:armhf (1.1.8-3.1+deb8u2, 1.1.8-3.1+deb8u2+b1), libpam-modules:armhf (1.1.8-3.1+deb8u2, 1.1.8-3.1+deb8u2+b1), libdns-export100:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), libxml2:armhf (2.9.1+dfsg1-5+deb8u4, 2.9.1+dfsg1-5+deb8u5), multiarch-support:armhf (2.19-18+deb8u9, 2.19-18+deb8u10), linux-image-next-sunxi:armhf (5.31, 5.32), linux-headers-next-sunxi:armhf (5.31, 5.32), libcurl3:armhf (7.38.0-4+deb8u5, 7.38.0-4+deb8u6), libgcrypt20:armhf (1.6.3-2+deb8u2, 1.6.3-2+deb8u4), debconf:armhf (1.5.56, 1.5.56+deb8u1), libisccc90:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), debian-archive-keyring:armhf (2014.3, 2017.5~deb8u1), libc6:armhf (2.19-18+deb8u9, 2.19-18+deb8u10), libisc-export95:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), libc6-dev:armhf (2.19-18+deb8u9, 2.19-18+deb8u10), curl:armhf (7.38.0-4+deb8u5, 7.38.0-4+deb8u6), libsoup2.4-1:armhf (2.48.0-1, 2.48.0-1+deb8u1), gnupg:armhf (1.4.18-7+deb8u3, 1.4.18-7+deb8u4), libisc95:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), libbind9-90:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), perl-base:armhf (5.20.2-3+deb8u7, 5.20.2-3+deb8u9), libdns100:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), locales:armhf (2.19-18+deb8u9, 2.19-18+deb8u10), base-files:armhf (8+deb8u8, 8+deb8u9), debconf-i18n:armhf (1.5.56, 1.5.56+deb8u1), libffi6:armhf (3.1-2+b2, 3.1-2+deb8u1), liblwres90:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), libgnutls-deb0-28:armhf (3.3.8-6+deb8u5, 3.3.8-6+deb8u7), libc-dev-bin:armhf (2.19-18+deb8u9, 2.19-18+deb8u10), linux-libc-dev:armhf (3.16.43-2, 3.16.43-2+deb8u5), linux-dtb-next-sunxi:armhf (5.31, 5.32), libpam0g:armhf (1.1.8-3.1+deb8u2, 1.1.8-3.1+deb8u2+b1), bluez:armhf (5.23-2+b1, 5.23-2+deb8u1), libcurl3-gnutls:armhf (7.38.0-4+deb8u5, 7.38.0-4+deb8u6), libexpat1:armhf (2.1.0-6+deb8u3, 2.1.0-6+deb8u4), libisccfg90:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), dnsutils:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), mysql-common:armhf (5.5.55-0+deb8u1, 5.5.57-0+deb8u1), git:armhf (2.1.4-2.1+deb8u3, 2.1.4-2.1+deb8u5), libmysqlclient18:armhf (5.5.55-0+deb8u1, 5.5.57-0+deb8u1), gpgv:armhf (1.4.18-7+deb8u3, 1.4.18-7+deb8u4), bind9-host:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), libisccfg-export90:armhf (9.9.5.dfsg-9+deb8u11, 9.9.5.dfsg-9+deb8u14), libgnutls-openssl27:armhf (3.3.8-6+deb8u5, 3.3.8-6+deb8u7), wpasupplicant:armhf (2.3-1+deb8u4, 2.3-1+deb8u5), libc-bin:armhf (2.19-18+deb8u9, 2.19-18+deb8u10), git-man:armhf (2.1.4-2.1+deb8u3, 2.1.4-2.1+deb8u5)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2017-10-16  22:47:22

 

So just a wild guess, after upgrading the system my session variables were pointing to the wrong directory?

 

Well that's not it, I still have a session to my other bpi1, and when I type depmod command I have the same issue.. I've tried to reload the session variables, no luck.

 

 


root@bpi1:~# ls /lib/modules
4.11.6-sunxi
root@bpi1:~# depmod
depmod: ERROR: could not open directory /lib/modules/4.11.5-sunxi: No such file or directory
depmod: FATAL: could not search modules: No such file or directory

 

Uname also reports wrong kernel

 

root@bpi1:~# uname -r
4.11.5-sunxi

Anyway, it's a kernel upgrade which caused the issue, I guess you have to reboot anyway. I'm just curious why it didn't keep the old kernel, that's what I'm used to it.

 

Posted

Why do you have a "4.11.5-sunxi" kernel and have modules for "4.11.6-sunxi" ?

Did your system been upgraded and freshly installed ?

If upgrade, maybe something went wrong during upgrade ...

Freshly installed ! Almost impossible ...

 

I suggested to restart again from freshly install !

 

Posted

Sorry, I was rambling a bit it was kinda late.

 

It's a fresh install followed by an apt upgrade, then I've installed Docker.  I don't understand why the old modules are deleted before reboot.

 

Nevertheless the root cause is apt upgrade initiated a kernel update and removed the old modules.

 

A reboot fixed the issue because it reloaded the new kernel.

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines