Re: [PATCH v3 2/2] Documentation: dev-tools: add container.rst page

[Nathan Chancellor <nathan@kernel.org>]

Actually sending to Nicolas now :) sorry for the noise!

https://lore.kernel.org/linux-kbuild/20260120183550.GD2749368@ax162/

On Tue, Jan 20, 2026 at 11:35:50AM -0700, Nathan Chancellor wrote:
> 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):
>