Hi Guillaume, On Wed, Dec 31, 2025 at 05:51:48PM +0100, Guillaume Tucker wrote: > This proposal emerged from discussions over email and after a talk at > Plumbers 2024: > > > https://lore.kernel.org/all/[email protected]/ > > The aim is to facilitate reproducing builds for CI bots as well as > developers using containers. Here's an illustrative example with a > kernel.org toolchain in a Docker image from tuxmake: > > $ scripts/container -i tuxmake/korg-clang-21 make LLVM=1 defconfig > HOSTCC scripts/basic/fixdep > HOSTCC scripts/kconfig/conf.o > [...] > HOSTCC scripts/kconfig/util.o > HOSTLD scripts/kconfig/conf > *** Default configuration is based on 'x86_64_defconfig' > # > # configuration written to .config > # > > This patch series also includes a documentation page with all the > relevant details and further examples about how to use the tool. > > To go one step further, I'm in the process of preparing reference > container images with kernel.org toolchains and no third-party > dependencies other than the base Debian distro. See this thread for > more details and options to host them in an upstream way: > > > https://lore.kernel.org/all/[email protected]/ > > Say, to run KUnit using the latest kernel.org GCC toolchain: > > scripts/container --shell \ > -i registry.gitlab.com/gtucker/korg-containers/gcc:kunit -- \ > tools/testing/kunit/kunit.py \ > run \ > --arch=x86_64 \ > --cross_compile=x86_64-linux-
I went over the script and the documentation and it looks pretty good to me at this point. My only comment would be potentially referencing the TuxMake container images in the example section to give folks a "prebuilt" container option while getting the kernel.org container images sorted out but that can always be done in a follow-up change. I will apply this to kbuild-next-unstable shortly to give folks a week or so to voice any objections or give critical review comments. Cheers, Nathan
