Repository navigation
support --env-file in docker-compose run command #8379
Description
NOTE: this is different than the .env file that is read by docker-compose commands and used for substitutions in the composition file... first mentioned here: #6170 (comment)
We generate an env file that we would like to include via the docker-compose run command. e.g.
echo "FOO=bar" > vars.env
docker-compose run --env-file=vars.env --rm test-service
docker run supports this flag and it would be great if we saw docker-compose run maintain parity.
Is there planned support for this feature -- or will it be implemented in composev2 / "docker compose" ?
our generated vars file is cumbersome (with multiline values) and relatively complicated to convert to various -e FOO=bar flags...
thanks!
Activity
KoditkarVedant commentedon Feb 13, 2022
@chris-crone @ndeloof Hi guys, I would like to work on this issue. I am not new to Go lang.
I have got a question. If I pass
--env-fileoption to run command then should we append that toenv-fileprovided as part of service config in docker-compose.yaml file or should we override them?KoditkarVedant commentedon Feb 13, 2022
In meantime I've created a draft PR which assumes that if you pass --env-file from CLI it overrides the env-file specified in docker-compose.yaml file. I will update PR as per your suggestion if we should append them.
KoditkarVedant commentedon Feb 25, 2022
@chris-crone @ndeloof @ulyssessouza Friendly ping.
briceburg commentedon Jul 4, 2022
I would think would want to append the --env-file(s) passed via the cli to any included in the service's definition. appending would override any previously defined keys.
reggermont commentedon Jan 17, 2023
I'm surprised this issue hasn't more discussions.
Just had this case in a project and that's a deal breaker, will have to generate a huge
docker runcommand just because of that issueI think there's a misconception with the original
--env-fileoption which should never have the same name thandocker's--env-file.Now the topic is stuck because it may conflict with the original
--env-fileWhat about a
--env-frominstead?ndeloof commentedon Jan 18, 2023
That's indeed sad this flag name was selected, but this is the legacy we have to deal with.
We could use
--service-env-fileor something comparable, even verbose, to workaround this ambiguityKoditkarVedant commentedon Jan 24, 2023
@ndeloof I have updated the PR with changes suggested.