From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, f4bug@amsat.org,
aurelien@aurel32.net, pbonzini@redhat.com, stefanha@redhat.com,
crosa@redhat.com, "Stefan Weil" <sw@weilnetz.de>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>
Subject: [PATCH v1 1/9] Run docker probe only if docker or podman are available
Date: Tue, 8 Nov 2022 09:23:00 +0000 [thread overview]
Message-ID: <20221108092308.1717426-2-alex.bennee@linaro.org> (raw)
In-Reply-To: <20221108092308.1717426-1-alex.bennee@linaro.org>
From: Stefan Weil <sw@weilnetz.de>
The docker probe uses "sudo -n" which can cause an e-mail with a security warning
each time when configure is run. Therefore run docker probe only if either docker
or podman are available.
That avoids the problematic "sudo -n" on build environments which have neither
docker nor podman installed.
Fixes: c4575b59155e2e00 ("configure: store container engine in config-host.mak")
Signed-off-by: Stefan Weil <sw@weilnetz.de>
Message-Id: <20221030083510.310584-1-sw@weilnetz.de>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index 66928692b0..26c7bc5154 100755
--- a/configure
+++ b/configure
@@ -1780,7 +1780,7 @@ fi
# functions to probe cross compilers
container="no"
-if test $use_containers = "yes"; then
+if test $use_containers = "yes" && (has "docker" || has "podman"); then
case $($python "$source_path"/tests/docker/docker.py probe) in
*docker) container=docker ;;
podman) container=podman ;;
--
2.34.1
next prev parent reply other threads:[~2022-11-08 9:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 9:22 [PATCH v1 for 7.2 0/9] test and doc updates Alex Bennée
2022-11-08 9:23 ` Alex Bennée [this message]
2022-11-08 9:23 ` [PATCH v1 2/9] tests/avocado: improve behaviour waiting for login prompts Alex Bennée
2022-11-08 11:23 ` Philippe Mathieu-Daudé
2022-11-08 21:19 ` John Snow
2022-11-08 9:23 ` [PATCH v1 3/9] tests/avocado/machine_aspeed.py: Reduce noise on the console for SDK tests Alex Bennée
2022-11-08 9:23 ` [PATCH v1 4/9] tests/docker: allow user to override check target Alex Bennée
2022-11-08 11:12 ` Philippe Mathieu-Daudé
2022-11-08 9:23 ` [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start Alex Bennée
2022-11-08 9:32 ` Michael S. Tsirkin
2022-11-08 10:23 ` Alex Bennée
2022-11-08 10:26 ` Michael S. Tsirkin
2022-11-08 11:21 ` Alex Bennée
2022-11-08 15:24 ` Michael S. Tsirkin
2022-11-08 16:41 ` Alex Bennée
2022-11-08 9:33 ` Michael S. Tsirkin
2022-11-14 16:18 ` Christian Borntraeger
2022-11-14 16:37 ` Michael S. Tsirkin
2022-11-14 16:55 ` Christian Borntraeger
2022-11-14 17:10 ` Michael S. Tsirkin
2022-11-14 17:15 ` Christian Borntraeger
2022-11-14 17:20 ` Michael S. Tsirkin
2022-11-15 7:44 ` Christian Borntraeger
2022-11-15 8:18 ` Christian Borntraeger
2022-11-15 9:05 ` Michael S. Tsirkin
2022-11-15 11:25 ` Michael S. Tsirkin
2022-11-15 13:25 ` Christian Borntraeger
2022-11-15 14:31 ` Alex Bennée
2022-11-15 15:09 ` Christian Borntraeger
2022-11-15 16:05 ` Alex Bennée
2022-11-15 16:40 ` Christian Borntraeger
2022-11-15 16:46 ` Christian Borntraeger
2022-11-21 22:37 ` Michael S. Tsirkin
2022-11-23 6:27 ` Christian Borntraeger
2022-11-14 16:43 ` Alex Bennée
2022-11-08 9:23 ` [PATCH v1 6/9] docs/devel: add a maintainers section to development process Alex Bennée
2022-11-08 9:23 ` [PATCH v1 7/9] docs/devel: make language a little less code centric Alex Bennée
2022-11-08 9:23 ` [PATCH v1 8/9] docs/devel: simplify the minimal checklist Alex Bennée
2022-11-08 9:23 ` [PATCH v1 9/9] docs/devel: try and improve the language around patch review Alex Bennée
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=20221108092308.1717426-2-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).