From: Coiby Xu <coiby.xu@gmail.com>
To: Guillaume Tucker <gtucker@gtucker.io>
Cc: linux-doc@vger.kernel.org, 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: Thu, 25 Jun 2026 18:05:32 +0800 [thread overview]
Message-ID: <ajz8qtGkafGZnCPv@Rk> (raw)
In-Reply-To: <df2fd6ae-69bd-42e6-bf28-ad8103b4189f@gtucker.io>
On Wed, Jun 24, 2026 at 11:02:49PM +0200, Guillaume Tucker wrote:
>Hi Coiby,
Hi Guillaume,
>
>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 for taking time to reviewing the patch!
>
>Thanks,
>Guillaume
>
--
Best regards,
Coiby
next prev parent reply other threads:[~2026-06-25 10:05 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
2026-06-25 10:05 ` Coiby Xu [this message]
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=ajz8qtGkafGZnCPv@Rk \
--to=coiby.xu@gmail.com \
--cc=corbet@lwn.net \
--cc=gtucker@gtucker.io \
--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 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.