Skip to content
This repository has been archived by the owner on Feb 12, 2021. It is now read-only.

Latest commit

 

History

History
65 lines (47 loc) · 2.41 KB

kernel-modules.md

File metadata and controls

65 lines (47 loc) · 2.41 KB
Raw

Building custom kernel modules

Create a writable overlay

The kernel modules directory /lib/modules is read-only on Container Linux. A writable overlay can be mounted over it to allow installing new modules.

modules=/opt/modules  # Adjust this writable storage location as needed.
sudo mkdir -p "$modules" "$modules.wd"
sudo mount \
    -o "lowerdir=/lib/modules,upperdir=$modules,workdir=$modules.wd" \
    -t overlay overlay /lib/modules

To mount the overlay automatically when the system boots, add the following line to /etc/fstab (creating it if necessary).

overlay /lib/modules overlay lowerdir=/lib/modules,upperdir=/opt/modules,workdir=/opt/modules.wd,nofail 0 0

Prepare a CoreOS Container Linux development container

Read system configuration files to determine the URL of the development container that corresponds to the current Container Linux version.

. /usr/share/coreos/release
. /usr/share/coreos/update.conf
url="http://${GROUP:-stable}.release.core-os.net/$COREOS_RELEASE_BOARD/$COREOS_RELEASE_VERSION/coreos_developer_container.bin.bz2"

Download, decompress, and verify the development container image.

gpg2 --recv-keys 04127D0BFABEC8871FFB2CCE50E0885593D2DCB4  # Fetch the buildbot key if neccesary.
curl -L "$url" |
    tee >(bzip2 -d > coreos_developer_container.bin) |
    gpg2 --verify <(curl -Ls "$url.sig") -

Start the development container with the host's writable modules directory mounted into place.

sudo systemd-nspawn \
    --bind=/lib/modules \
    --image=coreos_developer_container.bin

Now, inside the container, fetch the Container Linux package definitions, then download and prepare the Linux kernel source for building external modules.

emerge-gitclone
emerge -gKv coreos-sources
gzip -cd /proc/config.gz > /usr/src/linux/.config
make -C /usr/src/linux modules_prepare

Build and install kernel modules

At this point, upstream projects' instructions for building their out-of-tree modules should work in the Container Linux development container. New kernel modules should be installed into /lib/modules, which is bind-mounted from the host, so they will be available on future boots without using the container again.

In case the installation step didn't update the module dependency files automatically, running the following command will ensure commands like modprobe function correctly with the new modules.

sudo depmod