Skip to content
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 not found in Ubuntu 24.04 #9864

Closed
2 of 14 tasks
daveisfera opened this issue May 16, 2024 · 7 comments
Closed
2 of 14 tasks

docker-compose not found in Ubuntu 24.04 #9864

daveisfera opened this issue May 16, 2024 · 7 comments

Comments

@daveisfera
Copy link

Description

Docker Compose v2 2.27.0 is listed as available on Ubuntu 24.04 but running docker-compose says that it's not found

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 11
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

20240510.1.0

https://github.com/awresports/awresports-server/actions/runs/9105296423/job/25030858761

Is it regression?

Yes

Expected behavior

docker-compose would work on Ubuntu 24.04 like it did on Ubuntu 22.04

Actual behavior

docker-compose is not found

Repro steps

  1. Run a task that uses docker-compose
  2. Observe that it errors out after not being found
@kojoru
Copy link

kojoru commented May 16, 2024

docker-compose is a command for running Compose V1, but this image has Compose V2. Please see the migration guide. In simple cases it boils down to removing the dash, i. e. running docker compose instead of docker-compose.

Compose V1 will also be removed from other images in July.

@erik-bershel
Copy link
Contributor

Hey @daveisfera!

@kojoru sent an exceptionally correct answer already. We have plans to remove Docker Compose V1 at all, and for beta image it was decided to do it from the start. Please update your workflows to work with the current Docker Compose V2 or install old version in runtime.

@daveisfera
Copy link
Author

I understand that compose has been added to docker and that's the recommend path forward, but I believe that docker-compose is a stand alone tool and on macOS and the linux distributions I've used, you can run docker-compose --version and it will output something like this since it's a stand alone program:

Docker Compose version v2.27.0-desktop.2

@janbrasna
Copy link

@daveisfera You're probably just observing https://docs.docker.com/compose/migrate/#how-do-i-switch-to-compose-v2 Docker Desktop doing this shim for your convenience behind the scenes…

techamigo pushed a commit to Autorama/autorama-reusable-github-workflows that referenced this issue Aug 23, 2024
The ubuntu image does not support Docker compose V1 since 29th July 2024. So moving to use Docker Compose V2. Here is the reference actions/runner-images#9864
louije added a commit to gip-inclusion/gip-inclusion-website that referenced this issue Sep 10, 2024
Instead of `docker-compose`. Cf. actions/runner-images#9864.

Might fix some CI errors.
@daveisfera
Copy link
Author

Hey @daveisfera!

@kojoru sent an exceptionally correct answer already. We have plans to remove Docker Compose V1 at all, and for beta image it was decided to do it from the start. Please update your workflows to work with the current Docker Compose V2 or install old version in runtime.

Definitely agree with removing old/deprecated software as new images become available, but @erik-bershel can you explain why it was removed from old images? Is there an official lifecycle/support document about runner images and GitHub actions?
(I was just reminded of this concern because of the sudden breaking change that's happening with the cache action)

@erik-bershel
Copy link
Contributor

Hey @daveisfera!

We do not provide LTS versions of images. All images (except deprecated) are constantly changing to ensure security, quality and provide more features. We are also forced to update the content to comply with both support policy and user requests.

@daveisfera
Copy link
Author

Thanks! The support policy is the info that I'm looking for.
I'm still not clear on why removing docker-compose from old/existing images was the right path forward, but I guess that's water under the bridge at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants