[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v10 04/10] qemu-binfmt-conf.sh: add QEMU_CREDENTIAL and QEMU_

From: Unai Martinez Corral
Subject: Re: [PATCH v10 04/10] qemu-binfmt-conf.sh: add QEMU_CREDENTIAL and QEMU_PERSISTENT
Date: Fri, 13 Mar 2020 01:09:57 +0100

2020/03/10 9:20, Laurent Vivier:
If variable are set to 'yes', how do you force the value to no with the
command line?

I believe you cannot. Do you mean the explanation should be reworded? Or that the feature should be implemented?
Please, refresh my memory, why do we need these variables?
Do you have an use case?

See https://patchew.org/QEMU/20190306031221.GA53@03612eec87fc/20190306044620.GC75@03612eec87fc/ I copy the relevant explanation below:

The main use case is to provide defaults when this script is included
in a docker container. There are three actors involved:

- Developers of QEMU providing some defaults in the script.
- Developer of a docker image including the script from upstream but
changing some defaults by setting envvars inside the container.
- User of the container that might want to override the settings
either by setting the envvars or through the command line.

If the entrypoint to the docker image is any script that executes
qemu-binfmt-conf.sh at some point, the user cannot provide options
through the command line. Envvars allow to do so, without requiring
the user to customize the docker image.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]