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 <[email protected]>
---
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 <[email protected]>
Thanks for taking time to reviewing the patch!
Thanks,
Guillaume
--
Best regards,
Coiby
