Kernel missing support for aufs-dkms

[bmweller]

Unable to install package aufs-dkms

apt install aufs-dkms

Setting up aufs-dkms (4.19+20190211-1) ...
Removing old aufs-4.19+20190211 DKMS files...

------------------------------
Deleting module version: 4.19+20190211
completely from the DKMS tree.
------------------------------
Done.
Loading new aufs-4.19+20190211 DKMS files...
It is likely that 4.19.50+ belongs to a chroot's host
Building for 4.19.50+, 4.19.50-v7+ and 4.19.50-v7l+
Building initial module for 4.19.50+
Error! Bad return status for module build on kernel: 4.19.50+ (armv6l)
Consult /var/lib/dkms/aufs/4.19+20190211/build/make.log for more information.

System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:

• Which model of Raspberry Pi? PiZeroW
• Which OS and version

Raspberry Pi reference 2019-06-20
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 150e25c4f8123a4c9c63e8dca1b4737fa6c1135c, stage2

• Which firmware version

vcgencmd version
Jun 20 2019 16:13:08 
Copyright (c) 2012 Broadcom

• Which kernel version

Linux raspberrypi 4.19.50+ #896 Thu Jun 20 16:09:52 BST 2019 armv6l GNU/Linux

make.log

DKMS make.log for aufs-4.19+20190211 for kernel 4.19.50+ (armv6l)
Mon 24 Jun 16:48:08 BST 2019
make: Entering directory '/var/lib/dkms/aufs/4.19+20190211/build'
-I/var/lib/dkms/aufs/4.19+20190211/build/include -DCONFIG_AUFS_FS_MODULE -UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_SBILIST
make -C /lib/modules/4.19.50+/build M=/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs EXTRA_CFLAGS="-I/var/lib/dkms/aufs/4.19+20190211/build/include -DCONFIG_AUFS_FS_MODULE -UCONFIG
_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_SBILIST" modules
make[1]: Entering directory '/usr/src/linux-headers-4.19.50+'
  GEN     /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/conf.str
  CC [M]  /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.o
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:33,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:134:2: error: unknown type name ‘vfs_readf_t’
  vfs_readf_t  si_xread;
  ^~~~~~~~~~~
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/super.h:135:2: error: unknown type name ‘vfs_writef_t’
  vfs_writef_t  si_xwrite;
  ^~~~~~~~~~~~
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:38,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:243:20: error: unknown type name ‘vfs_readf_t’; did you mean ‘key_ref_t’?
 ssize_t xino_fread(vfs_readf_t func, struct file *file, void *buf, size_t size,
                    ^~~~~~~~~~~
                    key_ref_t
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/branch.h:245:21: error: unknown type name ‘vfs_writef_t’; did you mean ‘key_ref_t’?
 ssize_t xino_fwrite(vfs_writef_t func, struct file *file, void *buf,
                     ^~~~~~~~~~~~
                     key_ref_t
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:46,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h: In function ‘au_vm_prfile_set’:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/file.h:334:7: error: ‘struct vm_area_struct’ has no member named ‘vm_prfile’; did you mean ‘vm_file’?
  vma->vm_prfile = file;
       ^~~~~~~~~
       vm_file
In file included from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/aufs.h:57,
                 from /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.c:25:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h: In function ‘vfsub_update_time’:
/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/vfsub.h:233:9: error: implicit declaration of function ‘update_time’; did you mean ‘pte_same’? [-Werror=implicit-function-declaration
]
  return update_time(h_inode, ts, flags);
         ^~~~~~~~~~~
         pte_same
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:304: /var/lib/dkms/aufs/4.19+20190211/build/fs/aufs/module.o] Error 1
make[1]: *** [Makefile:1517: _module_/var/lib/dkms/aufs/4.19+20190211/build/fs/aufs] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.19.50+'
make: *** [Makefile:47: fs/aufs/aufs.ko] Error 2
make: Leaving directory '/var/lib/dkms/aufs/4.19+20190211/build'

• Additional Context
  It appears kernel patches required for aufs module installation are not included in the RPI kernel distribution
  https://github.com/sfjro/aufs4-standalone/tree/aufs4.19.17%2B

 apply ./aufs4-base.patch to your kernel source files.
- apply ./aufs4-mmap.patch too.
- apply ./aufs4-standalone.patch too.

[pelwell]

We're unlikely to support a niche feature that has been rejected by the Linux devs and that requires custom patches to be applied. You can strengthen your case by explaining what AUFS is, why our users want it, and why it is better than any alternative solutions. As a general rule, features that increase the size of the base kernel or that slow operation even when the feature isn't used are very rarely accepted, so you might want to address the issue of resource utilisation in your request.

[hostingnuggets]

@pelwell If it is not possible to install the aufs-dkms package on Raspbian buster then it's simply not possible to install the official docker-ce package from docker.com [1] because aufs-dkms is a dependency of the docker-ce package. I think a lot of people will want to run a modern version of Docker on their new Raspi4 so this should be valid enough reason IMHO to get things working with AUFS on Raspbian. It used to work nicely on Raspbian stretch. So why not buster?

[1] https://docs.docker.com/install/linux/docker-ce/debian/

[jeanibarz]

Can anyone explain me how to install aufs-dkms on a Raspberry Pi 3B+ ? I have the same error :

It is likely that 4.19.50-v7+ belongs to a chroot's hostError! Bad return status for module build on kernel: 4.19.50+ (armv7l) Consult /var/lib/dkms/aufs/4.19+20190211/build/make.log for more information. dpkg: erreur de traitement du paquet aufs-dkms (--configure) : installed aufs-dkms package post-installation script subprocess returned error exit status 10 Des erreurs ont été rencontrées pendant l'exécution : aufs-dkms E: Sub-process /usr/bin/dpkg returned an error code (1)

And yes it seems that docker-ce doesn't work because of that 👎

[PhilippHeuer]

Here all commands i used to install docker ce 18.09.0 on Raspian Buster:

sudo apt-get update
apt-get install apt-transport-https ca-certificates software-properties-common
curl -fsSL https://yum.dockerproject.org/gpg | sudo apt-key add -
echo "deb https://download.docker.com/linux/raspbian/ stretch stable" > /etc/apt/sources.list.d/docker.list
apt install --no-install-recommends docker-ce
systemctl enable docker.service
systemctl start docker.service

You can't use the official debian repository, there is a special one for raspian: https://download.docker.com/linux/raspbian/
You will not need aufs-dkms in that case.

[oliverkurth]

@PhilippHeuer That does not work either. There is no buster in https://download.docker.com/linux/raspbian/ , so I tried stretch. Looks like it still wants to build aufs, and I am getting the same error:

Setting up aufs-dkms (4.19+20190211-1) ...
Loading new aufs-4.19+20190211 DKMS files...
It is likely that 4.19.50-v7+ belongs to a chroot's host
Building for 4.19.50+, 4.19.50-v7+ and 4.19.50-v7l+
Building initial module for 4.19.50+
Error! Bad return status for module build on kernel: 4.19.50+ (armv7l)
Consult /var/lib/dkms/aufs/4.19+20190211/build/make.log for more information.
dpkg: error processing package aufs-dkms (--configure):
 installed aufs-dkms package post-installation script subprocess returned error exit status 10

[oliverkurth]

Well, it does not seem to matter, it works anyway. I can run containers now.

Looks like the solution is to install with --no-install-recommends. This is from here: docker/for-linux#709

[PhilippHeuer]

Thanks for that, i manually uninstalled it because i thought that it was leftover by my earlier tries.
Added --no-install-recommends to my docker ce installation step.

Good to have a working script to reproduce my installation now.

[pelwell]

So where does that leave this issue?

[NobodyXu]

@hostingnuggets aufs-dkms is not a dependency of docker-ce, but a recommendation. You can use apt-cache show docker-ce to check that.

BTW, docker is not default to use aufs anymore; It now default prefer to use overlayfs2, which have been merged to the linux kernel mainline since 3.18.

So I think the proper fix is probably for docker repository for raspbian to remove the aufs-dkms from the recommended.

[hostingnuggets]

@NobodyXu thanks, that totally makes sense! I didn't notice that the aufs-dkms pacakge is only recommended and not mandatory. So it's all good as one can skip installing the recommended packages.

[bmweller]

Thank you, closing this request

[netwninja]

Here all commands i used to install docker ce 18.09.0 on Raspian Buster:

sudo apt-get update
apt-get install apt-transport-https ca-certificates software-properties-common
curl -fsSL https://yum.dockerproject.org/gpg | sudo apt-key add -
echo "deb https://download.docker.com/linux/raspbian/ stretch stable" > /etc/apt/sources.list.d/docker.list
apt install --no-install-recommends docker-ce
systemctl enable docker.service
systemctl start docker.service

You can't use the official debian repository, there is a special one for raspian: https://download.docker.com/linux/raspbian/
You will not need aufs-dkms in that case.

I just tested it on RaspPi 4 with Raspbain Lite on it. It worked