Fix: testcontainers docker api version #4207
Closed
+12
−3
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
github-actions
bot
added
dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this PR?
This PR updates the CI test environment configuration to ensure integration tests that rely on containerized services can reliably connect to the local container runtime after recent runner image updates. It does this by adding a small configuration file in the runtime environment (the docker client properties file) so the Docker client and server negotiate a compatible API version, preventing container-based test suites from aborting during setup.
Any related issues, documentation, discussions?
Related to recent CI runner image updates that changed Docker behavior and can cause container-based tests to abort when the Docker client API version is not explicitly configured.
How was this PR tested?
Ran the existing test suite in CI to verify that container-based integration test suites no longer abort during setup.
Confirmed that the workflow completes successfully with no aborted suites.
Was this PR authored or co-authored using generative AI tooling?
Reviewed by Gemini 3