-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make v2 our primary target version of Docker Compose #1179
Conversation
Unfortunately, I still have a problem with my version 😕
|
Hrm ... can you run with debugging turned on?
|
Might be a sed portability issue? I tested on macOS. |
Yep. This is the result.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AWESOME!
lol too close to home! 😅
|
#!/usr/bin/env sh
for dc in docker-compose-$1*; do
./$dc version | head -n1 | sed -E 's/^.* version:? v?([0-9.]+),?.*$/\1/'
./$dc version | head -n1 | gsed -E 's/^.* version:? v?([0-9.]+),?.*$/\1/'
echo
done
|
jk ba7f951 😬 |
Hmm ... your review didn't clear the bit, @BYK. I guess I would need to give yinz write access. |
With this PR I am closing the Support for Docker Compose v2 milestone. Anything coming in we will treat as a regression. |
The big thing here is a fix for #1132. I did a grep for
docker-compose
and cleaned up the rest of the instances. The one question I had is in CI tests ... as I read it we still needdocker-compose
there so we can test v1, which we do still want to support for now.