From: Guillaume Tucker <gtucker@gtucker.io>
To: Coiby Xu <coiby.xu@gmail.com>, linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
"open list:DOCUMENTATION PROCESS" <workflows@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: dev-tools: scripts/container prefers Podman
Date: Wed, 24 Jun 2026 23:02:49 +0200 [thread overview]
Message-ID: <df2fd6ae-69bd-42e6-bf28-ad8103b4189f@gtucker.io> (raw)
In-Reply-To: <20260624013850.1853171-1-coiby.xu@gmail.com>
Hi Coiby,
On 24/06/2026 03:38, Coiby Xu wrote:
> Obviously scripts/container prefers Podman over Docker. Putting podman
> before docker also makes it consistent with following parts of the doc
> and the help text of the tool.
>
> Signed-off-by: Coiby Xu <coiby.xu@gmail.com>
> ---
> Documentation/dev-tools/container.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/dev-tools/container.rst b/Documentation/dev-tools/container.rst
> index 452415b64662..9e23f79d5ae1 100644
> --- a/Documentation/dev-tools/container.rst
> +++ b/Documentation/dev-tools/container.rst
> @@ -40,7 +40,7 @@ Available options:
>
> ``-r, --runtime RUNTIME``
>
> - Container runtime name. Supported runtimes: ``docker``, ``podman``.
> + Container runtime name. Supported runtimes: ``podman``, ``docker``.
>
> If not specified, the first one found on the system will be used
> i.e. Podman if present, otherwise Docker.
> @@ -75,8 +75,8 @@ working directory and adjust the user and group id as needed.
>
> The container image which would typically include a compiler toolchain is
> provided by the user and selected via the ``-i`` option. The container runtime
> -can be selected with the ``-r`` option, which can be either ``docker`` or
> -``podman``. If none is specified, the first one found on the system will be
> +can be selected with the ``-r`` option, which can be either ``podman`` or
> +``docker``. If none is specified, the first one found on the system will be
> used while giving priority to Podman. Support for other runtimes may be added
> later depending on their popularity among users.
>
It's a very subtle tweak but it does help avoid some confusion.
Reviewed-by: Guillaume Tucker <gtucker@gtucker.io>
Thanks,
Guillaume
next prev parent reply other threads:[~2026-06-24 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 1:38 [PATCH] Documentation: dev-tools: scripts/container prefers Podman Coiby Xu
2026-06-24 21:02 ` Guillaume Tucker [this message]
2026-06-25 10:05 ` Coiby Xu
2026-06-30 19:52 ` Jonathan Corbet
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=df2fd6ae-69bd-42e6-bf28-ad8103b4189f@gtucker.io \
--to=gtucker@gtucker.io \
--cc=coiby.xu@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--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