From: Nathan Chancellor <nathan@kernel.org>
To: "Guillaume Tucker" <gtucker@gtucker.io>,
"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 2/2] Documentation: dev-tools: add container.rst page
Date: Tue, 20 Jan 2026 11:35:50 -0700 [thread overview]
Message-ID: <20260120183550.GD2749368@ax162> (raw)
In-Reply-To: <aW-I3fNqp_7X0oeg@derry.ads.avm.de>
On Tue, Jan 20, 2026 at 02:53:33PM +0100, Nicolas Schier wrote:
> I probably have just read it over: I have to prefix the
> 'tuxmake/korg-clang' by 'docker.io/'. Is that a problem of my system
> configuration (Debian forky, no special podman config)?
Some distributions ship registries.conf [1] to allow unqualified image
names but I do not think Debian does. Personally, I use the full name
regardless but it should be easy to create it for commands such as these
to work. I use:
unqualified-search-registries = ['docker.io', 'ghcr.io', 'quay.io']
[1]: https://podman.io/docs/installation#registriesconf
> I tested a tiny bit with podman as runtime backend. If I leave out the
> '-r podman' podman's docker emulation is in effect and fails with:
>
> $ scripts/container -i docker.io/tuxmake/korg-clang -- make LLVM=1 -j8 olddefconfig
> Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
> mkdir: cannot create directory '.tmp_15': Permission denied
> mkdir: cannot create directory '.tmp_19': Permission denied
> mkdir: cannot create directory '.tmp_22': Permission denied
> mkdir: cannot create directory '.tmp_25': Permission denied
> mkdir: cannot create directory '.tmp_28': Permission denied
> mkdir: cannot create directory '.tmp_31': Permission denied
> HOSTCC scripts/basic/fixdep
> error: error opening 'scripts/basic/.fixdep.d': Permission denied
> 1 error generated.
> make[2]: *** [scripts/Makefile.host:114: scripts/basic/fixdep] Error 1
> make[1]: *** [/src/Makefile:655: scripts_basic] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
> [exit code 2]
>
> But with '-r podman' it works like a charm.
>
> Would it make sense to switch the default runtime to podman to
> prevent non-functional podman-docker emulation? (Or is this just a
> problem on my machine?)
Yeah, I think it would be better to prefer podman over docker if both
existed on the system. Something like this should do that?
diff --git a/scripts/container b/scripts/container
index dbe92630f05b..50c4ae851001 100755
--- a/scripts/container
+++ b/scripts/container
@@ -105,7 +105,7 @@ class PodmanRuntime(CommonRuntime):
class Runtimes:
"""List of all supported runtimes"""
- runtimes = [DockerRuntime, PodmanRuntime]
+ runtimes = [PodmanRuntime, DockerRuntime]
@classmethod
def get_names(cls):
next prev parent reply other threads:[~2026-01-20 18:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 16:51 [PATCH v3 0/2] scripts: introduce containerized builds 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 [this message]
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
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=20260120183550.GD2749368@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.