Repository navigation
ci: use docker compose v2 (fixes docker-compose command not found) - #1135
Conversation
ubuntu-24.04 (now ubuntu-latest) dropped the standalone docker-compose v1 binary, so the E2E job and the Makefile target failed with 'docker-compose: command not found'. Switch the command to 'docker compose' (v2, preinstalled on the runners). The docker-compose.test.yml filename is unchanged.
|
Warning Review limit reached
More reviews will be available in 15 minutes and 30 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
ci: use docker compose v2 (fixes docker-compose command not found)
Fixes the
docker-compose: command not foundCI failure.ubuntu-24.04 (now
ubuntu-latest) dropped the standalonedocker-composev1 binary. Switched the E2E job (ci.yml) and the Makefile target todocker compose(v2, preinstalled on the runners). Thedocker-compose.test.ymlfilename is unchanged.Note: the E2E job is
continue-on-error: trueso this was a non-blocking red X; this makes it run correctly when it does run.