Release a version of S3Mock using a version of testcontainers compatible with Docker v29+ #2962
Description
Docker recently (November 2025) released v29, which updated their minimum API requirement, causing errors like this when using testcontainers:
[info] java.lang.IllegalStateException: Could not find a valid Docker environment. Please see logs and check configuration
[info] at org.testcontainers.dockerclient.DockerClientProviderStrategy.lambda$getFirstValidStrategy$7(DockerClientProviderStrategy.java:274)
[info] at java.base/java.util.Optional.orElseThrow(Optional.java:403)
[info] at org.testcontainers.dockerclient.DockerClientProviderStrategy.getFirstValidStrategy(DockerClientProviderStrategy.java:265)
[info] at org.testcontainers.DockerClientFactory.getOrInitializeStrategy(DockerClientFactory.java:154)
[info] at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:196)
[info] at org.testcontainers.DockerClientFactory$1.getDockerClient(DockerClientFactory.java:108)
[info] at com.github.dockerjava.api.DockerClientDelegate.authConfig(DockerClientDelegate.java:109)
[info] at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:321)
See:
- Issue: [Bug]: Docker 29.0.0 could not find a valid Docker environment testcontainers/testcontainers-java#11212
- Fixed by: Set default docker API version to 1.44 testcontainers/testcontainers-java#11216
- Released in: v1.21.4 & v2.0.2
The latest released version of S3Mock is v4.11.0, which uses v1.21.3 - just too early for the fix which came in v1.21.4.
It looks like the unreleased v5.0.0 of S3Mock would have a sufficient update to resolve this problem:
- S3Mock 5.0.0 #2453 - includes an update to
testcontainers-javav2.0.2 - 5.0.0 maintenance #2820
GitHub Actions recently started the update to this version of Docker:
Could you release a version of S3Mock that has the latest testcontainers update, so the S3MOck works with recent versions of Docker?