TBD•3mo ago

docker-compose Failure

So I'm seeing transient failures, for instance here:

Run docker-compose up -d dwn-server
/home/runner/work/_temp/2d83f0ca-d1b7-4caf-ac8c-c0168939c60a.sh: line 1: docker-compose: command not found
Error: Process completed with exit code 127.

Run docker-compose up -d dwn-server
/home/runner/work/_temp/2d83f0ca-d1b7-4caf-ac8c-c0168939c60a.sh: line 1: docker-compose: command not found
Error: Process completed with exit code 127.

There's a whole bunch of similar failures here. I don't have an immediate idea to fix. If anyone does, that'd be great. If our builds start breaking it'll slow us down as we're integrating.

1 Reply

ALR•3mo ago

Well, would you look at that.

If you've encountered the error "docker-compose command not found" on or after April 2, 2024, it means you're using the v1 Docker Compose command.

If you've encountered the error "docker-compose command not found" on or after April 2, 2024, it means you're using the v1 Docker Compose command.

I'm going to see if I can force through a fix. And this is why it's transient, as it's rolling out to all Ubuntu and Windows images and isn't yet complete. I think this fixed it. Because transient, can't be sure. Folks in other OSS projects did similar, like this. @devRel Action for y'all - rebase your open PRs atop main to pick up this latest fix, and I think you should be good again. Finn, Leo - an interesting case for the "pro" side to lock runners, build tools, etc. to explicit versions rather than "latest". There are plenty of reasons to always use latest like we are, and this is the flip side of that coin. Build environment changing under our feet. 🙂

Gaming

Programming

docker-compose Failure