All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 0/4] tests/docker: improve detection of docker/podman
Date: Thu, 5 Feb 2026 18:17:26 +0000	[thread overview]
Message-ID: <aYTethv3y5HcIIt2@redhat.com> (raw)
In-Reply-To: <20260107130145.1495219-1-berrange@redhat.com>

Ping: any thoughts on this series of CI improvements ?

On Wed, Jan 07, 2026 at 01:01:41PM +0000, Daniel P. Berrangé wrote:
> 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.
> 
> Daniel P. Berrangé (4):
>   tests/docker: improve handling of docker probes
>   tests/docker: allow display of docker output
>   gitlab: ensure docker output is always displayed in CI
>   tests/docker: add support for podman remote access
> 
>  .gitlab-ci.d/base.yml         |  3 +++
>  configure                     | 19 +++++++------------
>  tests/docker/Makefile.include | 23 ++++++++++++++---------
>  tests/docker/docker.py        | 17 +++++++----------
>  4 files changed, 31 insertions(+), 31 deletions(-)
> 
> -- 
> 2.52.0
> 

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      parent reply	other threads:[~2026-02-05 18:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 13:01 [PATCH 0/4] tests/docker: improve detection of docker/podman Daniel P. Berrangé
2026-01-07 13:01 ` [PATCH 1/4] tests/docker: improve handling of docker probes Daniel P. Berrangé
2026-02-06 13:43   ` Thomas Huth
2026-01-07 13:01 ` [PATCH 2/4] tests/docker: allow display of docker output Daniel P. Berrangé
2026-02-06 13:48   ` Thomas Huth
2026-02-06 13:58     ` Daniel P. Berrangé
2026-01-07 13:01 ` [PATCH 3/4] gitlab: ensure docker output is always displayed in CI Daniel P. Berrangé
2026-02-06 13:49   ` Thomas Huth
2026-01-07 13:01 ` [PATCH 4/4] tests/docker: add support for podman remote access Daniel P. Berrangé
2026-02-05 18:17 ` Daniel P. Berrangé [this message]

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