From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
berrange@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] docker.py: always use --rm
Date: Thu, 17 Sep 2020 17:52:59 +0100 [thread overview]
Message-ID: <87een0xs44.fsf@linaro.org> (raw)
In-Reply-To: <faab2d69-4bd1-4878-d638-4c9414e56499@amsat.org>
Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
> On 9/17/20 12:44 PM, 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) \
>> $(if $(DEBUG),-ti,) \
>
> Alternatively:
>
> - $(if $V,,--rm)
> - $(if $(DEBUG),-ti,)
> + $(if $(DEBUG),-ti,--rm)
Surely that should b:
$(if $(DEBUG),-ti --rm,)
I think being able to keep the container around is useful for debug, I
have no problem with changing the behaviour for V=1.
>
> Anyhow:
> Acked-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>
>> $(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:
>>
--
Alex Bennée
next prev parent reply other threads:[~2020-09-17 16:58 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é
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 [this message]
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=87een0xs44.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--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 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).