Skip to content

ci: use the docker compose plugin and pin the test runner - #225

Merged
howethomas merged 1 commit into
mainfrom
ci/docker-compose-plugin
Nov 3, 2026
Merged

howethomas merged 1 commit into
mainfrom
ci/docker-compose-plugin

Conversation

@howethomas

Copy link
Copy Markdown
Contributor

Problem

The Python conserver unit test job fails on every PR and on main without running a test. ubuntu-latest moved from ubuntu-24.04 (last green run, 2026-10-11) to ubuntu-26.04. On the new image apt-get install -y docker-compose succeeds but leaves no docker-compose binary, so the first compose step exits 127 with docker-compose: command not found.

Change

  • Drop the apt install. Call Compose v2 through the docker compose plugin that GitHub runners ship, in all five places.
  • Add a docker compose version step up front, so a missing plugin fails with a clear message.
  • Pin runs-on: ubuntu-24.04 so the next change to ubuntu-latest is a deliberate bump with a green run, not a silent break.

No step depends on v1-style container names. The compose file parses under v2 (docker compose config lists redis, api, conserver).

Testing

This PR's own run is the test.

🤖 Generated with Claude Code

…4.04

ubuntu-latest moved to ubuntu-26.04, where apt no longer provides the
standalone docker-compose, so the test job failed at its first compose
step on every PR and on main without running a test. Call the Compose v2
plugin the runner ships, check for it up front, and pin the image so the
next default change is a deliberate bump.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@howethomas
howethomas merged commit 323109a into main Nov 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant