[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d4020305-fc95-446f-b73c-5f0be68529c9@gtucker.io>
Date: Wed, 21 Jan 2026 11:13:54 +0100
From: Guillaume Tucker <gtucker@...cker.io>
To: Nathan Chancellor <nathan@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
David Gow <davidgow@...gle.com>, Onur Özkan
<work@...rozkan.dev>, Nicolas Schier <nsc@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
rust-for-linux@...r.kernel.org, linux-kbuild@...r.kernel.org,
automated-testing@...ts.yoctoproject.org, workflows@...r.kernel.org,
llvm@...ts.linux.dev
Subject: Re: [PATCH v3 0/2] scripts: introduce containerized builds
Hi Nicolas,
On 20/01/2026 2:54 pm, Nicolas Schier wrote:
> Out-of-source builds do not work on my system with podman. If this is
> expected, I think it would be great to mention that somewhere in the
> documentation.
Yes, as discussed with Nathan. So here's the list of potential
improvements gathered so far:
* automatically pick Podman first, Docker second
* explicitly mention docker.io registry in examples
* mention TuxMake available images more explicitly in the docs
* mention that out-of-tree builds aren't supported yet
* distinguish true Docker from Docker-compatible Podman
* add support for out-of-tree output build directory
* add option for mounting source tree from arbitrary path
(needed for nested containers e.g. Docker-in-Docker)
* detect when Docker has namespace support enabled and document
* add user config file with default images and runtime etc.
Then beyond that we could consider other container runtimes such as
containerd, lxc, runc or whatever works in practice.
> Nevertheless, thanks a lot! I expect me to use that a lot in the
> future!
>
> For the whole patch set:
> Tested-by: Nicolas Schier<nsc@...nel.org>
> Acked-by: Nicolas Schier<nsc@...nel.org>
Thank you! Let's hope others will find it useful too.
Cheers,
Guillaume
Powered by blists - more mailing lists