From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] docker.py: always use --rm
Date: Thu, 17 Sep 2020 11:48:17 +0100 [thread overview]
Message-ID: <20200917104817.GE1568038@redhat.com> (raw)
In-Reply-To: <20200917104441.31738-1-pbonzini@redhat.com>
On Thu, Sep 17, 2020 at 12:44:41PM +0200, Paolo Bonzini wrote:
> Avoid that containers pile up.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> tests/docker/Makefile.include | 1 -
> tests/docker/docker.py | 4 ++--
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/tests/docker/Makefile.include b/tests/docker/Makefile.include
> index 3daabaa2fd..75704268ff 100644
> --- a/tests/docker/Makefile.include
> +++ b/tests/docker/Makefile.include
> @@ -243,7 +243,6 @@ docker-run: docker-qemu-src
> $(DOCKER_SCRIPT) run \
> $(if $(NOUSER),,--run-as-current-user) \
> --security-opt seccomp=unconfined \
> - $(if $V,,--rm) \
I guess the intention was that if someone is running verbose they might
want to get back into the container after a failure. This is certainly
a pain for CI though, because running verbose is desirable but keeping
around dead containers is not.
The DEBUG=1 option is likely a better general purpose debugging approach
than relying on the dead container being left behind, so
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> $(if $(DEBUG),-ti,) \
> $(if $(NETWORK),$(if $(subst $(NETWORK),,1),--net=$(NETWORK)),--net=none) \
> -e TARGET_LIST=$(subst $(SPACE),$(COMMA),$(TARGET_LIST)) \
> diff --git a/tests/docker/docker.py b/tests/docker/docker.py
> index 356d7618f1..36b7868406 100755
> --- a/tests/docker/docker.py
> +++ b/tests/docker/docker.py
> @@ -377,7 +377,7 @@ class Docker(object):
> if self._command[0] == "podman":
> cmd.insert(0, '--userns=keep-id')
>
> - ret = self._do_check(["run", "--label",
> + ret = self._do_check(["run", "--rm", "--label",
> "com.qemu.instance.uuid=" + label] + cmd,
> quiet=quiet)
> if not keep:
> @@ -616,7 +616,7 @@ class CcCommand(SubCommand):
> if argv and argv[0] == "--":
> argv = argv[1:]
> cwd = os.getcwd()
> - cmd = ["--rm", "-w", cwd,
> + cmd = ["-w", cwd,
> "-v", "%s:%s:rw" % (cwd, cwd)]
> if args.paths:
> for p in args.paths:
> --
> 2.26.2
>
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 :|
next prev parent reply other threads:[~2020-09-17 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 10:44 [PATCH] docker.py: always use --rm Paolo Bonzini
2020-09-17 10:48 ` Daniel P. Berrangé [this message]
2020-09-17 10:49 ` Paolo Bonzini
2020-09-17 10:48 ` no-reply
2020-09-17 10:49 ` no-reply
2020-09-17 13:38 ` Philippe Mathieu-Daudé
2020-09-17 16:52 ` Alex Bennée
2020-09-17 16:58 ` Paolo Bonzini
2020-09-17 18:50 ` Alex Bennée
2020-09-18 12:36 ` Peter Maydell
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=20200917104817.GE1568038@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.