Kernel missing support for aufs-dkms #3021
Comments
|
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. |
|
@pelwell If it is not possible to install the |
|
Can anyone explain me how to install aufs-dkms on a Raspberry Pi 3B+ ? I have the same error :
And yes it seems that docker-ce doesn't work because of that 👎 |
|
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.serviceYou can't use the official debian repository, there is a special one for raspian: https://download.docker.com/linux/raspbian/ |
|
@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: |
|
Well, it does not seem to matter, it works anyway. I can run containers now. Looks like the solution is to install with |
|
Thanks for that, i manually uninstalled it because i thought that it was leftover by my earlier tries. Good to have a working script to reproduce my installation now. |
|
So where does that leave this issue? |
|
@hostingnuggets BTW, So I think the proper fix is probably for |
|
@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. |
|
Thank you, closing this request |
I just tested it on RaspPi 4 with Raspbain Lite on it. It worked |
|
I was running zfs on my ubuntu 18.04. I have changed the storage driver to zfs and the docker booted correctly. |
add --no-install-recommends option to apt to avoid problems with afs dkms (see here: raspberrypi/linux#3021)
|
This is my conclusion.
This is Docker's problem. Docker has an independent release repository for Raspbian. They should remove Before they fix it, add a preference control file for APT can prevent Let's see the difference. Run Run I'll recommend to do this rather than set |
|
Its not just Docker though the problem is the complete lack of tools for overlayFS. You can do some really cool things with union filesystems such as using a zram ram upper over a large sd card lower and periodic merge down to create extremely low write resiliant file systems. I am not sure why overlayFS dev stopped with just docker but seems like it did. |
|
@pelwell I just ended up here because the auto installer for Nextcloud debian pi is attempting to install aufs-dkms https://raw.githubusercontent.com/nextcloud/nextcloudpi/master/install.sh I have no idea about the history here, and can do the patches. Just thought I'd let yall know that they appear to be currently leaning on that. |
|
DKMS make.log for aufs-4.19+20190211 for kernel 4.19.97+ (armv7l) |
This is indeed what solved my problem with aufs-dkms. Adding --no-install-recommends to your docker install might fix your issue, it did fix mine |
Unable to install package aufs-dkms
apt install aufs-dkms
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:
make.log
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
The text was updated successfully, but these errors were encountered: