don't skip compose
used as project name
#10657
Merged
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.
What I did
fix support for converting
docker-compose --project-name compose
into a compose v2 command (docker <space> compose
)Tried to understand the fix in #8985 to skip
compose
argument but doesn't make any sense to me after 18 months. This code is only used if command isdocker-compose ..
but not when used as a CLI plugin withdocker compose ...
, maybe this wasn't the case earlier? @ulyssessouza do you remember?Related issue
fixes #10647
(not mandatory) A picture of a cute animal, if possible in relation to what you did