Re: Kernel modules being built, but not being included in image

["S. Lockwood-Childs" <sjl@vctlabs.com>]

On Thu, Jan 10, 2019 at 04:49:36PM +0000, Muhlenkamp, Lewis wrote:
> Hello,
> 
> TLDR: How do I get docker fully functional in my openembedded linux image?
> 
> I've been trying to get docker included into my image.  All of my attempts lead to the same error messages appearing in the log file, and docker not starting.
> 
...
> 
> 
> That didn't seem to work either.  The modules always got built.  For example, br_netfilter.ko is built:
> 
...
> 
> But these modules are not included in my image.  
> For example, if I do "find / -name br_netfilter.ko" on my target install, nothing is returned.

Kernel modules are not installed into an image by default; this gives
the opportunity to choose on a per-image basis which modules are actually needed.
Then the same kernel can be used on both a tiny rescue image and a full 
production image. Each image recipe gets to list which modules it actually wants.

The core image recipe is a general one and meant to be lean, so it makes sense for 
this image to not include any modules in its package list. You can either inherit
from it for a custom recipe or use CORE_IMAGE_EXTRA_INSTALL as you have been doing.

If you don't feel like choosing each module, quick fix is to add "kernel-modules" 
to your CORE_IMAGE_EXTRA_INSTALL to ask for all that got built by your kernel config.

--SJLC