Arch Linux

originalsurfmex

Member

Registered: 2008-11-13

Posts: 150

using docker.io - patched kernel not loading AUFS [SOLVED hackily]

I am using docker (docker.io) and have installed the 'aufs_friendly' kernel and added it to my boot loader.  Despite everything appearing to work well on the surface, docker is not running.  This is the error i get:

└──>>docker run base echo 'test'
2013/09/26 23:08:59 Error: Error starting container cd07e1698f79: Unable to load the AUFS module

I am booting the kernel (according to uname -r anyway).  So far I have: reinstalled the kernel, reran mkinitcpio on both the patched and vanilla kernels, reran grub-mkconfig, tried running "sudo modprobe aufs" and reinstalled lxc-docker from AUR.  None of those methods have worked, "modprobe aufs" gave me an error "function not implemented".

Is there a way to debug what appears to blocking the AUFS module?  It does not appear on the list in /proc/filesystems, shouldn't it appear there?

Anyway, I'd like to confirm that the AUFS module is indeed loading or loadable.

Thanks for considering.

Last edited by originalsurfmex (2013-09-27 14:36:40)

originalsurfmex

Member

Registered: 2008-11-13

Posts: 150

Re: using docker.io - patched kernel not loading AUFS [SOLVED hackily]

I did some digging around and solved my problem - although it is kind of a hacky solution.

I checked the 'journalctl -xn' and found this '...loop_backing_file() is not defined'

The answer was found here http://www.mail-archive.com/aufs-users@ … 04375.html

Re: Linux 3.11-rc7: loop_backing_file() is not defined

Florian Klink Thu, 26 Sep 2013 11:50:04 -0700

   The error message also appears when both "aufs" and "loop" are compiled as a
   module.
   The problem is that depmod doesn't detect "loop" as a dependency module of
   "aufs".  So  you need to manually load "loop", then "aufs" (happens in
   Archlinux linux-zen kernel, for example).
   I got the following answer about it:

   Depmod only figures out dependencies via undefined symbols. AUFS doesn't
   call loop_backing_file directly, it just redirects it. Seems that this
   doesn't create a detectable dependency.
   Is there anything you can do about this?
   Florian
   Am 02.09.2013 00:00, schrieb [1]sf...@users.sourceforge.net:

With this in mind edited /etc/modules-load.d/modules.conf to show:

#trying desperately to load aufs module
loop
aufs

Now docker (docker.io) works fine.

Last edited by originalsurfmex (2013-09-27 14:35:13)