docker-compose: command not found in action, which was working yesterday

[gszentesi]

Select Topic Area

Bug

Body

Hi, I have a serious issue for a while. One of our repo the CI pipeline fails with the error: "docker-compose: command not found" at different steps. Sometimes the action survives the first step "Build integration test environment" sometimes does not. Then another step fails with the similar error.

My coworkers notified me that they have similar sporadic issues.

The first error:

And the second one:

This pipeline is fine since years. There where no change in the pipeline since 6 months. I have no more clue what to do or what to fix, because since the last successful execution happened last week, and there were no change in the pipeline, just in the code.

Could someone suggest anything to be able to fix this?

Thanks
G

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[gszentesi]

Furthermore I tried now to execute the action was successfully run 1 week ago, and I got very similar error:

[GithmiHashara]

Try these solutions;

1. Check Installation:

Ensure docker-compose is installed in your CI environment.
Use which docker-compose or docker-compose --version to verify.

2. Update Pipeline Config:

Add a step in your CI pipeline to install docker-compose:
(yaml)

`

• run: |
  curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
  chmod +x /usr/local/bin/docker-compose
  `

3. Check PATH:

Ensure the installation directory is in the system's PATH.

4. Rebuild Cache:

Clear any cached layers in your CI environment to apply the changes.

[gszentesi]

Thank you for your quick answer,

I added the docker-compose version verification step just as you mentioned and it is working.

I am wondering why 😲,
but once more thanks for your hint!

Cheers
G

[grandmas-favorite]

Nice one @GithmiHashara! 😁

[NaveedAhmadHematmal]

I tried but was not working, adding a 'v' before the version number on URL worked for me.

[yoannchaudet]

Looks like this is a change introduced by actions/runner-images#9692.

The real fix is to update your workflow from calling docker-compose to just docker compose. As per https://github.blog/changelog/2024-04-10-github-hosted-runner-images-deprecation-notice-docker-compose-v1 🎉

[alexgleith]

Thanks!