iotedge: Issue installing IoTEdge on RPI4 (Errors were encountered while processing: aufs-dkms)

Expected Behavior

Following the guide at https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux-arm to install moby and iotedge on an Rpi4 (it seems like the guide only include stretch right now so im not sure if IoTEdge is supported on the Rpi4 yet?)

Installation should go well and iotedge should start working.

Current Behavior

Cannot get past “install moby-cli”

Steps to Reproduce

  1. Setup a fresh rpi4 with buster
  2. Follow the steps in the guide
  3. When running step to install moby-cli error occures

Context (Environment)

Device (Host) Operating System

Raspberry Pi 4 Model B Raspbian GNU/Linux 10 (buster) Linux raspberrypi 4.19.46-v7l+ #866 SMP Fri Jun 7 18:00:39 BST 2019 armv7l GNU/Linux

Architecture

arm32

Container Operating System

Linux

Runtime Versions

Logs

Logs from going through the steps of the guide (following raspbian stretch)
pi@raspberrypi:~ $ curl https://packages.microsoft.com/config/debian/stretch/multiarch/prod.list > ./microsoft-prod.list
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   104  100   104    0     0    249      0 --:--:-- --:--:-- --:--:--   250
pi@raspberrypi:~ $ sudo cp ./microsoft-prod.list /etc/apt/sources.list.d/
pi@raspberrypi:~ $ curl https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   983  100   983    0     0   2996      0 --:--:-- --:--:-- --:--:--  3006
pi@raspberrypi:~ $ sudo cp ./microsoft.gpg /etc/apt/trusted.gpg.d/
pi@raspberrypi:~ $ sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:3 https://packages.microsoft.com/debian/stretch/multiarch/prod stretch InRelease [23.0 kB]
Get:4 https://packages.microsoft.com/debian/stretch/multiarch/prod stretch/main all Packages [546 B]
Get:5 https://packages.microsoft.com/debian/stretch/multiarch/prod stretch/main amd64 Packages [1,230 B]
Get:6 https://packages.microsoft.com/debian/stretch/multiarch/prod stretch/main armhf Packages [2,863 B]
Get:7 https://packages.microsoft.com/debian/stretch/multiarch/prod stretch/main arm64 Packages [1,236 B]
Reading package lists... Done
E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
pi@raspberrypi:~ $ sudo apt-get install moby-engine
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  aufs-dkms aufs-tools cgroupfs-mount dkms raspberrypi-kernel-headers
Suggested packages:
  aufs-dev python3-apport menu
The following NEW packages will be installed:
  aufs-dkms aufs-tools cgroupfs-mount dkms moby-engine raspberrypi-kernel-headers
0 upgraded, 6 newly installed, 0 to remove and 93 not upgraded.
Need to get 52.3 MB of archives.
After this operation, 281 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.raspberrypi.org/debian buster/main armhf raspberrypi-kernel-headers armhf 1.20190819-1 [24.9 MB]
Get:2 http://raspbian.playstar.se/raspbian buster/main armhf dkms all 2.6.1-4 [74.4 kB]
Get:3 http://raspbian.playstar.se/raspbian buster/main armhf aufs-dkms all 4.19+20190211-1 [183 kB]
Get:4 https://packages.microsoft.com/debian/stretch/multiarch/prod stretch/main armhf moby-engine armhf 3.0.6 [27.0 MB]
Get:5 http://raspbian.playstar.se/raspbian buster/main armhf aufs-tools armhf 1:4.14+20190211-1 [103 kB]
Get:6 http://raspbian.playstar.se/raspbian buster/main armhf cgroupfs-mount all 1.4 [6,276 B]
Fetched 52.3 MB in 7s (7,298 kB/s)
Selecting previously unselected package dkms.
(Reading database ... 132894 files and directories currently installed.)
Preparing to unpack .../0-dkms_2.6.1-4_all.deb ...
Unpacking dkms (2.6.1-4) ...
Selecting previously unselected package aufs-dkms.
Preparing to unpack .../1-aufs-dkms_4.19+20190211-1_all.deb ...
Unpacking aufs-dkms (4.19+20190211-1) ...
Selecting previously unselected package aufs-tools.
Preparing to unpack .../2-aufs-tools_1%3a4.14+20190211-1_armhf.deb ...
Unpacking aufs-tools (1:4.14+20190211-1) ...
Selecting previously unselected package cgroupfs-mount.
Preparing to unpack .../3-cgroupfs-mount_1.4_all.deb ...
Unpacking cgroupfs-mount (1.4) ...
Selecting previously unselected package moby-engine.
Preparing to unpack .../4-moby-engine_3.0.6_armhf.deb ...
Unpacking moby-engine (3.0.6) ...
Selecting previously unselected package raspberrypi-kernel-headers.
Preparing to unpack .../5-raspberrypi-kernel-headers_1.20190819-1_armhf.deb ...
Unpacking raspberrypi-kernel-headers (1.20190819-1) ...
Setting up aufs-tools (1:4.14+20190211-1) ...
Setting up dkms (2.6.1-4) ...
Setting up raspberrypi-kernel-headers (1.20190819-1) ...
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.19.66+
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.19.66-v7+
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.19.66-v7l+
Setting up moby-engine (3.0.6) ...
Adding group `docker' (GID 115) ...
Done.
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
Setting up aufs-dkms (4.19+20190211-1) ...
Loading new aufs-4.19+20190211 DKMS files...
It is likely that 4.19.46-v7l+ belongs to a chroot's host
Building for 4.19.46+, 4.19.46-v7+, 4.19.46-v7l+, 4.19.66+, 4.19.66-v7+ and 4.19.66-v7l+
Module build for kernel 4.19.46+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Module build for kernel 4.19.46-v7+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Module build for kernel 4.19.46-v7l+ was skipped since the
kernel headers for this kernel does not seem to be installed.
Building initial module for 4.19.66+
Error! Bad return status for module build on kernel: 4.19.66+ (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
Setting up cgroupfs-mount (1.4) ...
Processing triggers for systemd (241-5+rpi1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Errors were encountered while processing:
 aufs-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

Additional Information

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 30 (13 by maintainers)

Most upvoted comments

Hi @darobs thanks this fixed the “buster InRelease’…” issue but I still get the following error when running

sudo apt-get install moby-engine

It is likely that 4.19.46-v7l+ belongs to a chroot's host
Building for 4.19.66+, 4.19.66-v7+ and 4.19.66-v7l+
Building initial module for 4.19.66+
Error! Bad return status for module build on kernel: 4.19.66+ (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
Errors were encountered while processing:
 aufs-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

But IoTEdge works fine.

This happened to me after accidentally installing Moby with an existing Docker installation. The Moby installation failed at that time but I ignored it since I thought it wouldn’t actually damage the entire configuration. But right after that I could not run apt-get anymore without getting that error no matter what I was installing / removing / etc.

So after a lot of trial and error, here’s a workaround that did the job for me.

I ran: sudo apt-get autoremove

This removed aufs-dkms for me which caused the problem. I got a kernel update prompt which I confirmed without changing anything and then rebooted the machine (sudo reboot) and ran:

sudo apt-get upgrade

Hope it helps someone.

I’m assuming the moby runtime is working fine because it chose to use the overlay2 filesystem instead of aufs. (https://docs.docker.com/storage/storagedriver/aufs-driver/)

You can find out which storage driver it’s using by finding the “Storage Driver” section in the docker info command.

It also looks like there’s a issue on the moby project related to this: https://github.com/moby/moby/issues/39542