fix: fix docker-compose API version incompatibility with updated dockerd#446
Merged
fix: fix docker-compose API version incompatibility with updated dockerd#446
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem
After upgrading the artsy dockerd to Docker 29.2.1 (API 1.53), CircleCI builds started failing to connect to the remote docker daemon with (e.g. exchange):
The new dockerd requires a minimum client API version of 1.44. While the docker CLI in the hokusai image (Docker 28.3.3, API 1.51) satisfied this requirement, docker-compose v2.20.3 was built against Docker API 1.43 — just one version below the minimum — causing all hokusai builds to fall back to CircleCI's own Docker daemon instead of the artsy remote dockerd.
Fix
Upgrade docker-compose from v2.20.3 to v2.40.3, which uses Docker API >= 1.44.