Documentation: dev-tools: scripts/container prefers Podman

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>
Reviewed-by: Guillaume Tucker <gtucker@gtucker.io>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20260624013850.1853171-1-coiby.xu@gmail.com>
This commit is contained in:
Coiby Xu 2026-06-24 09:38:50 +08:00 committed by Jonathan Corbet
parent b68f29353e
commit c2d0e81cb6

View File

@ -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.