On Raspberry Pi, BUILD_EXCLUSIVE directive does not match this kernel/arch

[smuda]

On Raspberry Pi, BUILD_EXCLUSIVE directive does not match this kernel/arch

[peter-hartmann]

sudo apt install raspberrypi-kernel-headers
... worked for me on RASPBIAN STRETCH LITE. I found that hint here: https://www.raspberrypi.org/forums/viewtopic.php?t=204433

Whereas
sudo apt-get -y install linux-headers-4.9.0-4-all raspberrypi-kernel-headers
gave me this error
E: Unable to locate package linux-headers-4.9.0-4-all

[telmomarques]

Apparently there's an issue with 18.09.1, but 18.06.1 works fine.

sudo apt-get remove docker-ce
sudo apt-get autoremove
sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian

I still got the "BUILD_EXCLUSIVE directive which
does not match this kernel/arch" error, but the service started fine this time:

pi@raspberrypi:~ $ sudo service docker status
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-01-21 23:43:42 GMT; 29s ago

Got hint from here:
docker/for-linux#490 (comment)

[fuglede]

FWIW, I'm seeing the exact same DKMS errors popping using the 18.06.1 build as suggested by @telmomarques, but the service runs regardless (which it wouldn't when using the most recent version). This is on a Raspberry Pi 1B+:

$ uname -a
Linux 4.1.19+ #858 Tue Mar 15 15:52:03 GMT 2016 armv6l GNU/Linux

$ sudo apt-get install docker-ce=18.06.1~ce~3-0~raspbian
...
The following additional packages will be installed:
  aufs-dkms aufs-tools cgroupfs-mount dkms linux-headers-3.6-trunk-common linux-headers-3.6-trunk-rpi linux-kbuild-3.6
  linux-kbuild-4.9 pigz
...
Setting up docker-ce (18.06.1~ce~3-0~raspbian) ...
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
[ ok ] Starting Docker: docker.
Setting up linux-headers-3.6-trunk-common (3.6.9-1~experimental.1+rpi7) ...
Setting up cgroupfs-mount (1.3) ...
[ ok ] Mounting cgroupfs hierarchy.
...
Building initial module for 3.6-trunk-rpi
Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
Skipped.
...

$ sudo service docker status
[ ok ] Docker is running.

Nevertheless, the hello-world image doesn't quite seem to work:

$ docker run hello-world
docker: Error response from daemon: cgroups: cannot find cgroup mount destination: unknown.
ERRO[0008] error waiting for container: context canceled

As a next step, I tried the solution outlined here. With this, a container runs but exits with no output and no logs.

$ sudo mkdir /sys/fs/cgroup/systemd
$ sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd
$ docker run hello-world

Inspired by this StackOverflow answer the next observation is that the image is indeed an ARM one, yet only after using hypriot/armhf-hello-world instead did I get the expected output:

$ docker image inspect hello-world | grep Architecture
        "Architecture": "arm",
$ docker run hypriot/armhf-hello-world
Hello from Docker.
This message shows that your installation appears to be working correctly.

[smuda]

In the end, what was missing was installing the linux headers:

sudo apt-get -y install linux-headers-4.9.0-4-all raspberrypi-kernel-headers

Should that have been part of the installation script? I really don't know, so I'll leave that to you. 😇

[ericcurtin]

I'd open the PR for you @smuda if I could find out where the .deb dependencies are listed in github.

https://download.docker.com/linux/raspbian/dists/stretch/stable/binary-armhf/Packages

If these two packages were listed as dependencies you wouldn't have seen an issue.

I am not a docker employee.

[ericcurtin]

I'm not running Raspbian, so I'm not much help unfortunately.

😟

But to me it looks like a problem with "Raspbian Stretch Lite" rather than the installation script.

Hope somebody can help you out!

[smuda]

thanks @ericcurtin . As the installation of docker worked with the same version of Raspbian Stretch on the 18th of september, I'd suspect this is something within the dependencies of docker.

But you're right, I currently don't suspect the installation script. I'll just head over to https://github.com/docker/for-linux instead.

[jtmoon79]

I ran into this problem using Raspberry Pi 2 hardware running Raspbian Debian 9.6 Stretch. I'm reposting a few notes in case others run into this and have some brilliant ideas. Between these steps I was entirely removing docker-ce (apt-get remove docker-ce followed by apt-get autoremove followed by apt-get clean sometimes followed by apt-get update).
Tragically, I couldn't find a workaround in my case.

Stretch vs. Stretch Lite ?

First, I'm using plain Raspbian Stretch and not Raspbian Stretch Lite. Using Stretch Lite was suggested in this blog post. AFAICT, that shouldn't make a difference ... but maybe?

Following official install docs

I didn't use docker-install, I followed the instructions at Get Docker CE for Debian, but the results probably would have been the same.

I tried a few different permutations of instructions at Get Docker CE for Debian plus the workarounds mentioned in this thread.

dkms?

Here are some of the concerning messages during apt-get install docker-ce

Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of dkms (? 2.3-2) <Resolved in some Version>
 b1 - #884658 - dkms: Should really depends on dpkg-dev for dpkg-architecture (Fixed: dkms/2.6.1-2)
Summary:
 dkms(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] Y

...

Created symlink /etc/systemd/system/multi-user.target.wants/docker.service ? /lib/systemd/system/docker.service.
Job for docker.service canceled.
docker.service couldn't start.
Setting up aufs-dkms (4.9+20161219-1) ...
Loading new aufs-4.9+20161219 DKMS files...
It is likely that 4.14.79+ belongs to a chroot's host
Building for 3.6-trunk-rpi, 4.14.79+ and 4.14.79-v7+
Building initial module for 3.6-trunk-rpi
Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
Skipped.
Module build for kernel 4.14.79+ was skipped since the
kernel headers for this kernel does not seem to be installed.

...

And when run

# docker run armhf/hello-world
Illegal instruction

I changed the line in /usr/src/aufs-4.9+20161219/dkms.conf to be removed.
I also tried it set to empty string BUILD_EXCLUSIVE_KERNEL="".
Neither helped.

raspberrypi-kernel-headers ?

I installed raspberrypi-kernel-headers but that didn't help.

arch ?

I tried the workaround mentioned here (e.g. try [arch=arm32v6] instead of [arch=armhf] within /etc/apt/sources.list.d/docker.list). That didn't help.

That recounting wasn't exhaustive nor in exact same order but it hit the major points.

Sad day :-(

[KEINOS]

F.Y.I @smuda's comment @peter-hartmann's comment worked for me! Thanks!!

• RaspberryPi Zero W(ARMv6l) + Stretch Lite (2019-04-08-raspbian-stretch-lite)
• The Errors I got:

Building initial module for 4.19.66+
Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
Skipped.

Building initial module for 4.19.66-v7+
Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch.  This indicates that it should not be built.
Skipped.

• Success Steps To Install Docker(on brand new installed Stretch on RPiZeroW):

$ date -R
Fri, 27 Sep 2019 11:53:38 +0900
$ curl -fsSL https://download.docker.com/linux/raspbian/gpg | sudo apt-key add -
$ # The missing apt of the error
$ sudo apt install raspberrypi-kernel-headers
$ sudo vi /etc/apt/sources.list.d/docker.list
...
$ cat /etc/apt/sources.list.d/docker.list
deb [arch=armhf] https://download.docker.com/linux/raspbian stretch stable

$ sudo apt update
...
$ sudo apt-get install docker-ce=18.06.2~ce~3-0~raspbian
...

$ sudo docker version
Client:
 Version:           18.06.2-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        6d37f41
 Built:             Sun Feb 10 03:57:32 2019
 OS/Arch:           linux/arm
 Experimental:      false

Server:
 Engine:
  Version:          18.06.2-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       6d37f41
  Built:            Sun Feb 10 03:53:01 2019
  OS/Arch:          linux/arm
  Experimental:     false
$ # 🎉