workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"David Gow" <davidgow@google.com>,
	"Onur Özkan" <work@onurozkan.dev>,
	"Arnd Bergmann" <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	linux-kbuild@vger.kernel.org,
	automated-testing@lists.yoctoproject.org,
	workflows@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3 0/2] scripts: introduce containerized builds
Date: Mon, 19 Jan 2026 14:35:16 -0700	[thread overview]
Message-ID: <20260119213516.GA1051134@ax162> (raw)
In-Reply-To: <cover.1767199119.git.gtucker@gtucker.io>

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/affb7aff-dc9b-4263-bbd4-a7965c19ac4e@gtucker.io/
> 
> 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/cc737636-2a43-4a97-975e-4725733f7ee4@gtucker.io/
> 
> 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

  parent reply	other threads:[~2026-01-19 21:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-31 16:51 Guillaume Tucker
2025-12-31 16:51 ` [PATCH v3 1/2] scripts: add tool to run " Guillaume Tucker
2025-12-31 16:51 ` [PATCH v3 2/2] Documentation: dev-tools: add container.rst page Guillaume Tucker
2026-01-20 13:53   ` Nicolas Schier
2026-01-20 18:35     ` Nathan Chancellor
2026-01-20 18:39       ` Nathan Chancellor
2026-01-21  9:55       ` Guillaume Tucker
2026-01-22  4:55         ` Nathan Chancellor
2026-01-22 14:25           ` Guillaume Tucker
2026-01-22 10:13     ` Guillaume Tucker
2026-01-16 10:28 ` [PATCH v3 0/2] scripts: introduce containerized builds Guillaume Tucker
2026-01-16 21:12   ` Nathan Chancellor
2026-01-19 14:22     ` Guillaume Tucker
2026-01-19 21:35 ` Nathan Chancellor [this message]
2026-01-19 21:49   ` Nathan Chancellor
2026-01-20  9:56     ` Guillaume Tucker
2026-01-20 17:58       ` Nathan Chancellor
2026-01-20  9:46   ` Guillaume Tucker
2026-01-20 17:55     ` Nathan Chancellor
2026-01-20 13:54 ` Nicolas Schier
2026-01-20 18:04   ` Nathan Chancellor
2026-01-21 10:13   ` Guillaume Tucker
2026-01-22 14:12   ` Guillaume Tucker
2026-01-27 20:13     ` Nicolas Schier
2026-01-31 13:36       ` Guillaume Tucker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260119213516.GA1051134@ax162 \
    --to=nathan@kernel.org \
    --cc=arnd@arndb.de \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=davidgow@google.com \
    --cc=gtucker@gtucker.io \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=work@onurozkan.dev \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox