From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH v2 0/4] tests/docker: improve detection of docker/podman
Date: Tue, 10 Feb 2026 16:35:52 +0000 [thread overview]
Message-ID: <20260210163556.713841-1-berrange@redhat.com> (raw)
This improves integration such that tests/docker/Makefile.include will
correctly honour the exact command detected by docker.py's probing
logic. Currently the probe command gets stripped down to just a bare
'podman' or 'docker' command name. This means while commands run via
'docker.py' would use 'sudo -n docker', commands run directly from
Makefile.include would only use 'docker'.
This series fixes that so that 'docker.py probe' correctly reports the
full argv, and configure honours that argv untouched.
With that fixed, we can then also add support for 'podman --remote'
and 'podman-remote', which allow use of podman when already inside
podman which is the scenario for my development environment that is
using 'toolbox'.
Finally this also improves CI by ensuring that stdout from docker is
not thrown away, so we can have a chance of diagnosing build failures
from CI.
Changed in v2:
- Fix misc typos
- Default $(DOCKER_V) value from $(V)
Daniel P. Berrangé (4):
tests/docker: improve handling of docker probes
tests/docker: add support for podman remote access
tests/docker: allow display of docker output
gitlab: ensure docker output is always displayed in CI
.gitlab-ci.d/base.yml | 3 +++
configure | 19 +++++++------------
tests/docker/Makefile.include | 25 ++++++++++++++++---------
tests/docker/docker.py | 17 +++++++----------
4 files changed, 33 insertions(+), 31 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-10 16:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 16:35 Daniel P. Berrangé [this message]
2026-02-10 16:35 ` [PATCH v2 1/4] tests/docker: improve handling of docker probes Daniel P. Berrangé
2026-02-10 16:35 ` [PATCH v2 2/4] tests/docker: add support for podman remote access Daniel P. Berrangé
2026-03-02 7:51 ` Thomas Huth
2026-07-09 14:48 ` Pierrick Bouvier
2026-07-09 15:40 ` Daniel P. Berrangé
2026-07-09 15:55 ` Pierrick Bouvier
2026-07-09 16:01 ` Daniel P. Berrangé
2026-07-09 16:04 ` Pierrick Bouvier
2026-07-09 16:15 ` Daniel P. Berrangé
2026-07-09 16:13 ` Daniel P. Berrangé
2026-07-09 16:24 ` Pierrick Bouvier
2026-07-10 8:06 ` Daniel P. Berrangé
2026-07-10 11:47 ` Alex Bennée
2026-07-10 11:52 ` Daniel P. Berrangé
2026-07-10 18:20 ` Pierrick Bouvier
2026-07-13 8:32 ` Daniel P. Berrangé
2026-07-13 16:01 ` Pierrick Bouvier
2026-02-10 16:35 ` [PATCH v2 3/4] tests/docker: allow display of docker output Daniel P. Berrangé
2026-03-02 8:07 ` Thomas Huth
2026-07-10 11:36 ` Alex Bennée
2026-02-10 16:35 ` [PATCH v2 4/4] gitlab: ensure docker output is always displayed in CI Daniel P. Berrangé
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=20260210163556.713841-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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.