From: "Theodore Tso" <tytso@mit.edu>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Guillaume Tucker" <gtucker@gtucker.io>,
"Ben Copeland" <ben.copeland@linaro.org>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Onur Özkan" <work@onurozkan.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
workflows@vger.kernel.org,
automated-testing@lists.yoctoproject.org,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Subject: Re: Hosting first-party kernel.org container images
Date: Thu, 19 Mar 2026 10:15:34 -0400 [thread overview]
Message-ID: <20260319141534.GB91368@macsyma-wired.lan> (raw)
In-Reply-To: <CANiq72=t=q4__vwTFjg+gQyjKLUEJrZBngr3cAnnKiTNM5uteg@mail.gmail.com>
On Thu, Mar 19, 2026 at 12:10:19PM +0100, Miguel Ojeda wrote:
>
> While many kernel developers may not use them (mostly because everyone
> has their own setup already), if we had a set of "base" images that
> are maintained by someone trusted (including publishing them in the
> usual registries for easy use), then I think a bunch of us would
> actually use them for CI and possibly other tasks; just like some of
> us already use the kernel.org toolchains "manually" anyway etc.
I publish test appliance images suitable for use by kvm-xfstests and
android-xfstests on www.kernel.org[1], and have for years. A
description of how they are generated, and what I do in order to keep
the GPL complaint can be described in this slide deck[2]. In
particular, note how I am very careful to explicitly specify where the
corresponding source can be found in a README file[3]. This is
required by the GPL, so that someone can recreate the binary image
using the exact sources that were used to generate them. I've noted
that not all container / docker images seem to follow the letter of
the law, and fortunately various groups such as the SFLC hasn't gone
after people who publish these images.... but I think it's better to
be careful about such things.
[1] https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests/
[2] https://thunk.org/gce-xfstests
[3] https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests/README
My kvm-xfstests images are relatively small, and I don't update them
all that often, so I haven't had any complaints from the folks who
manage kernel.org about. So aside from the GPL compliance issues, if
you think that you might be making a large number of images, which
might be potentially large, you might want to check with them first.
Cheers,
- Ted
prev parent reply other threads:[~2026-03-19 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cc737636-2a43-4a97-975e-4725733f7ee4@gtucker.io>
[not found] ` <CAL0q8a7mepGUdgrLsQhCUdLVP8VcxB9x_oBRCWAYNeoVAUb=7A@mail.gmail.com>
2026-02-25 14:44 ` Hosting first-party kernel.org container images Guillaume Tucker
2026-03-10 0:48 ` Nathan Chancellor
2026-03-19 10:37 ` Guillaume Tucker
2026-03-19 11:10 ` Miguel Ojeda
2026-03-19 14:15 ` Theodore Tso [this message]
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=20260319141534.GB91368@macsyma-wired.lan \
--to=tytso@mit.edu \
--cc=arnd@arndb.de \
--cc=automated-testing@lists.yoctoproject.org \
--cc=ben.copeland@linaro.org \
--cc=gtucker@gtucker.io \
--cc=kernelci@lists.linux.dev \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@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