Replies: 4 comments 3 replies
-
I've been getting this sporadically today as well. To test that I wasn't going insane (because seemingly nothing changed with the code) - I reran the job with no new commits, submitted commits with comment changes and it seems to pass or fail at random times. I do use docker-compose so that could be the issue. I'll check out the discussion. Thanks for the link! |
Beta Was this translation helpful? Give feedback.
-
Comment of appreciation for this issue and leading us to a fix! 🤘🏻 |
Beta Was this translation helpful? Give feedback.
-
Change |
Beta Was this translation helpful? Give feedback.
-
weird, neither
|
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
If you've encountered the error "docker-compose command not found" on or about April 2, 2024, it means you're using the v1 Docker Compose command.
GitHub deprecated v1, and you need to change the command from, e.g.,
docker-compose build
todocker compose build
(remove the dash)There are other changes too, and your workflows and scripts might need migrations to v2. Take a look at the official Docker Compose V2 Migration Guide for guidance
In my case, I discovered that this change occurred when I also had to update my docker-compose.yml files so that each service with a healthcheck used in a
depends_on
hadcondition: "service_healthy"
. I'm unsure why this suddenly broke or if it's related, but perhaps the description will help someone. For example, I changed this......into this....
There is an active discussion thread in the repository where v1 was deprecated on the GitHub Actions Hosted Runners:
actions/runner-images#9557
Beta Was this translation helpful? Give feedback.
All reactions