Open vincentARM opened 5 years ago
Hi @vincentARM,
there are (deliberately) no kernel modules inside the container, since these are actually provided by the host system.
You can either build build your out-of-tree modules in the host (Raspbian) system (still a full 64-bit kernel, even though the userland is 32-bits); or, if you absolutely have to, you can always add the /lib/modules
directory to the container's list of bind mounts. To do the latter, edit the (host) file /etc/systemd/nspawn/debian-buster-64.nspawn
(as root, or using sudo
), and add to the [Files]
section:
Bind=/lib/modules
Leave the rest of the file as-is, and save. Stop and start the container again. You should now find the (host's) modules directory is present inside.
hth, sakaki
31 Oct 2020: sadly, due to legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the Debian package is still in the official Raspbian repos); however, there will be no further updates to the underlying OS images etc., nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice.
For further details, please see my post here.
With sincere apologies, sakaki ><
Hello. I have a problem to build kernel modules : the version /lib/modules/4.19.75-v8+ is not found in the container 64 bits. Thank for you help.