Due to a recent GitHub Actions runner change, runners have now dropped Docker Compose v1 in favor of v2. One of the more notable changes in v2 is that the docker-compose executable is no longer available, as one is intended to use docker compose (without a hyphen) instead. Unfortunately, our CI currently expects docker-compose (with the hyphen), which causes CI to fail with the following error (example):
/home/runner/work/_temp/09281912-1902-40ae-8041-59f8afe8b874.sh: line 1: docker-compose: command not found
We should repair the CI. It might be as simple as replacing docker-compose with docker compose—worth trying.
Just wanted to say thank you for creating this issue with clear description, docker-compose was failing in my builds and I was so lost why that was happening.
Due to a recent GitHub Actions runner change, runners have now dropped Docker Compose v1 in favor of v2. One of the more notable changes in v2 is that the
docker-compose
executable is no longer available, as one is intended to usedocker compose
(without a hyphen) instead. Unfortunately, our CI currently expectsdocker-compose
(with the hyphen), which causes CI to fail with the following error (example):We should repair the CI. It might be as simple as replacing
docker-compose
withdocker compose
—worth trying.