Re: Migration to Debian Bookworm and compiler updates for KernelCI

Mark Brown <[email protected]> Tue, 12 Mar 2024 13:11:32 +0000

Newsgroups	dev.linux.lists.kernelci,dev.linux.lists.llvm
Message-ID	<[email protected]>

On Mon, Mar 11, 2024 at 08:10:31PM +0100, Guillaume Tucker wrote:

> Then in addition to the tarballs, one thing that was discussed
> with Linaro in the very early days of tuxmake was to have a
> reference set of Docker image with the toolchains already
> installed - to save everyone creating their own like in Nathan's
> GitHub link.  Has anyone done that already?

Providing you don't mind ignoring the tuxmake install in them (or using
it) the tuxmake images kind of do that.  The KernelCI ones similarly
though they're only built when actually used so it's a much smaller set
of toolchains.

> I started looking into it while I was writing my tutorial to
> build a kernel last month but didn't find anything, so it's kind
> of going up on my TODO list now.  It would greatly help unify
> kernel builds across CI systems in particular and improve
> reproducibility.  The TuxBuild / tuxmake Docker images were
> forked from the KernelCI ones so that's already something that
> could be reunited at some point.

It is pretty sensible if you're doing a CI tool to put any tool specific
bits you need into the core docker image and then layer the specific
toolchains on top of that so I'm not sure how that scales in terms of
the actual images.  From a source code point of view you could do
something easily enough though with templating or a light fork for each
user that wants to customise the images.

signature.asc (application/pgp-signature, 488 B)