Update testcontainers to a version that works with Docker v29#136
Merged
Update testcontainers to a version that works with Docker v29#136
testcontainers to a version that works with Docker v29#136Conversation
So that tests run with the latest version of Docker Co-authored-by: Roberto Tyley <52038+rtyley@users.noreply.github.com> Co-authored-by: Marjan K <15894063+marjisound@users.noreply.github.com>
rtyley
approved these changes
Feb 20, 2026
testcontainers to a version that works with Docker v29
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.
The
etag-cachingproject has one test (S3ObjectFetchingTest) that depends on S3Mock/testcontainers-java and thus on Docker Containers. A recent version of Docker (v29, in November 2025) updated their Docker API requirement, meaning thatS3ObjectFetchingTestfails like this on dev laptops using recent versions of Docker Desktop:Note that this is also the same failure we see when Docker Desktop is not running on the machine.
GitHub Actions also recently adopted this version of Docker:
See:
We're using S3Mock v4.11.0, which is the latest version of S3Mock that's been released or tagged. However, it looks like there has been some (unreleased) work on v5.0.0 of S3Mock:
testcontainers-javav2.0.2...when that new version of S3Mock is released, we won't need to explicitly force the
testcontainers-javaupdate anymore.See also
S3ObjectFetchingTest#137