Explicitly mention ignoring variables not conforming to the desired format #9467
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Adjust spec for the
.envfile to adopt the de facto behaviour up until docker/compose@0612d97 was merged.Some users depended on lines starting with
exportbeing ignored by docker-compose so they could use the.envfile viasourcecommand or some other tools that also read the.envfile.The spec didn't say what would happen with lines not conforming to the syntax. Breakage ensured when the aforementioned merge request was pulled into docker-compose (docker/compose#6511 docker/compose#6838).
There is a feature request for a switch that would prevent docker-compose from reading
.envbut it only solves the problem ofI don't want docker-compose to use my .env file at all(docker/compose#6741). It's implemented in docker/compose#6850Related issues (optional)
docker/compose#6511
docker/compose#6838
docker/compose#6741
docker/compose#6850