Regarding immutability, it is a fair point. However, it is common within
the Docker world to modify environment variables, through Dockerfiles, the
docker run command, and within processes running inside the container too.
The first two of course are picked up through the s6-overlay setup, but the
On 11/05/2015 15:54, Gorka Lertxundi wrote:
Yes, it's safe. Every time "with-contenv" is invoked, current env is
dropped and the new one loaded with the current env file/vars
I know that - I wrote it - but my point was about immutability
guarantee. That envdir contains the environment as it is
2015-05-11 15:11 GMT+02:00 Laurent Bercot :
> On 11/05/2015 13:52, Scott Mebberson wrote:
>
>> I'm working on an addition to the s6-overlay project. I want to make it
>> super easy to create environment variables within a Docker container.
>>
>
> IIRC, /var/run/s6/container_environment is meant t
On 11/05/2015 13:52, Scott Mebberson wrote:
I'm working on an addition to the s6-overlay project. I want to make it
super easy to create environment variables within a Docker container.
IIRC, /var/run/s6/container_environment is meant to hold the variables
that the container is actually starte
I'm working on an addition to the s6-overlay project. I want to make it
super easy to create environment variables within a Docker container.
To execute the script:
script_name env_var_name env_var_value
This would create a file at /var/run/s6/container_environment/ENV_VAR_NAME,
with the content
