fix: docker-compose fails with multiple merge keys #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Docker compose no longer allows multiple merge keys in compose files. The YAML spec allows multiple maps to be merged by passing a sequence to the merge (`<<:`) key. This is documented in the [YAML spec](https://yaml.org/type/merge.html). The behavior change for docker-compose is documented in [this issue](docker/compose#10411)
abates
force-pushed
the
fix-docker-compose
branch
from
89955d5 to
cd51281
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Docker compose no longer allows multiple merge keys in compose files. The YAML spec allows multiple maps to be merged by passing a sequence to the merge (
<<:) key. This is documented in theYAML spec. The behavior change for docker-compose is documented in
this issue