-
Notifications
You must be signed in to change notification settings - Fork 269
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
[Docker Compose] V2 GA #256
Comments
Hi, Is this still "Almost There"? Are there any technical issue? |
Hi! Yes, still in almost there. We're going to time the GA with the next release of the CLI, which right now we don't have a definitive timeline for. We wanted to make sure there was an easy install path for Linux users before we called this GA. A bit more details here: https://docs.docker.com/compose/cli-command/#transitioning-to-ga-for-compose-v2 ! Let me know if that helps :) |
Any news on this? Looks like there's been two cli releases since the comment above (20.10.13 and 20.10.14) so did the transition to GA happen or is there something else holding it up? If it's still in progress, it would be useful to see the tickets that relate to that so it's clear what's outstanding. As it currently stands, it's very unclear just how GA-ready v2 is (so difficult to know whether to switch in an enterprise environment). |
Hi! We're very close to the announcement on GA (about a month or so), there are no technical barriers from using it in an enterprise environment. We had yet to call it generally available since prior to the 20.10.13 release it was not easily available to download on Linux, now that we have made it an optional plugin, we are working on transitioning our docs and guides to make v2 the default! |
The packages that have been made available have been very helpful! I can't wait to see a full inclusion into cli, and/or installation via https://github.com/docker/docker-install |
Hi all! Yesterday marked GA, check out the announcement here! |
This is great news! Is there a specific version of compose v2 that is considered GA? I ask because the latest version released on GitHub as of writing is 2.4.1 while the latest version available from the docker-ce repository is currently 2.3.3 (which has some issues that were fixed in 2.4.x such as docker/compose@85a4d04 ). Per a previous comment it seems like there is work being done to get the repository updated more regularly. Edit: There's actually some important fixes in https://github.com/docker/compose/commits/v2 that have not yet been released in a new version ( docker/compose@625a48d docker/compose@9cfea28 docker/compose@0da4543 ) |
@nemchik G.A doesn't apply to a specific version of compose v2, we use this terminology to qualify software being considered stable (while, obviously, some bugs still can exist) and available on all supported platform, which is the case as docker-ce-repository now offers compose v2 for Linux as system packages. Those are not updated yet with latest release but will be soon. We are also working on making our packaging pipeline more flexible so we can keep version in sync without such delays. |
Thanks for the follow up! I appreciate the explanation and all the work you've done! |
@stephanierifai Now that GA is announced, will new Compose V2 Docker images be released? This is the final blocker our company has to fully switching over to Compose V2. |
hi @johnthagen I think you saw, but we shipped it and now closed it! Thanks for the feedback :D |
Tell us about your request
Move Docker Compose v2 from release candidate to generally available and make it the default version for all OS.
Which service(s) is this request for?
Dev-tools
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Turning this option on by default in Docker Desktop users, will allows users can seamlessly move to Docker Compose V2 will help improve adoption, while still maintaining the flexibility to opt out.
Are you currently working around the issue?
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: