-
Notifications
You must be signed in to change notification settings - Fork 14
Open
Description
We have experience some churn in our usage of Docker in GitHub Actions lately. This account of events is based on my memory and thus possibly incomplete or wrong.
- Docker v29 is released. Presumably there is a corresponding release of
docker-buildx, which is versioned and released separately. Something changes in the release about the layout of metadata JSON emitted bydocker buildx. - February 9ish: GitHub updates Docker in the ubuntu-latest GH runner image to v29.1.* ([Windows/Ubuntu] Docker Server and Client will be updated to version 29.1.*, Docker Compose will be updated to version 2.40.3 on February 9th, 2026 actions/runner-images#13474).
- Janus CI jobs start failing.
- Janus takes a change to look for image SHAs in a new location (Revert _and_ Bake #4366,
release/0.7: fix bake target metadata #4367). CI works again. - February 19-20ish: GitHub rolls the Docker version on ubuntu-latest back due to people's jobs failing due to some other incompatibility across Docker versions ([Windows/Ubuntu] Docker Server and Client will be updated to version 29.1.*, Docker Compose will be updated to version 2.40.3 on February 9th, 2026 actions/runner-images#13474 (comment)).
- Janus CI breaks again (https://github.com/divviup/janus/actions/runs/22208701146/job/64238533069?pr=4371)
- Since our build tools work with Docker v29.1 and up, we adopt the
docker/setup-docker-actionaction to undo GitHub's rollback (Pin Docker v29.2.1 in CI #4376).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels