-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Ubuntu, Windows] Docker Compose v1 will be removed from images on July, 29 #9692
[Ubuntu, Windows] Docker Compose v1 will be removed from images on July, 29 #9692
Comments
I understand removing it from new images (like the Ubuntu 24.04 one that was just released), but why remove it from existing images? |
The removal of Docker Compose v1 is postponed till 29 of July. |
@Alexey-Ayupov And the variable: $(docker_compose_exe_path) is - an example:
|
@Alexey-Ayupov could you confirm if v2 executable will still be available at this path after the removal of v1? /usr/libexec/docker/cli-plugins/docker-compose Found out the answer after looking into the source code.
|
GitHub Actions removed docker-compose: actions/runner-images#9692 Also did some CQL and Dev Docs.
Docker compose v1 has been deprecated since July 2023 [1]. Now the GitHub actions Ubuntu runner images removed it, too [2]. So move to v2. labgrid is obviously not affected by any changes between v1 and v2 other than the compose call docker-compose -> docker compose. [1] https://docs.docker.com/compose/migrate/ [2] actions/runner-images#9692 Signed-off-by: Bastian Krause <bst@pengutronix.de>
* Linked to deprecation of Docker Compose v1 in Github Actions: actions/runner-images#9692 * Updates dependencies and fixes safety tests. Co-Authored-by: Pascal Repond <pascal.repond@rero.ch>
Thank you , Closing this issue as the Docker compose V1 got removed from both Windows and Ubuntu/MacOS images. |
Needed because of actions/runner-images#9692
`docker-compose` was removed in actions/runner-images#9692
v2 uses `docker compose` instead of `docker-compose`. Ubuntu gha runners now ship with v2 only, see actions/runner-images#9692
v2 uses `docker compose` instead of `docker-compose`. Ubuntu gha runners now ship with v2 only, see actions/runner-images#9692
v2 uses `docker compose` instead of `docker-compose`. Ubuntu gha runners now ship with v2 only, see actions/runner-images#9692
v2 uses `docker compose` instead of `docker-compose`. Ubuntu gha runners now ship with v2 only, see actions/runner-images#9692
v2 uses `docker compose` instead of `docker-compose`. Ubuntu gha runners now ship with v2 only, see actions/runner-images#9692
Breaking changes
Docker compose v1 will be removed from Ubuntu & Windows images.
Target date
The images rollout process will start on July, 29 and take 3-4 days.
The motivation for the changes
Docker compose v1 has been deprecated since July 2023 and customers are encouraged to migrate to v2, apart from that, as per our support policy it has been more that 6 months since the deprecation announcement so we would like to finally remove it. More information can also be found on the GitHub blog.
Possible impact
If your pipelines or workflows still depend on docker compose v1 they might be broken.
Platforms affected
Runner images affected
Mitigation ways
The last release of the v1 branch is still available on GitHub and can be downloaded and installed manually in runtime for both Ubuntu and Windows.
The text was updated successfully, but these errors were encountered: