Mr-w-22 commented on issue #37642: URL: https://github.com/apache/shardingsphere/issues/37642#issuecomment-3875317813
> ## Feature Request > **For English only**, other languages will not be accepted. > > Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot make decision by current information, we will **close it**. > > Please answer these questions before submitting your issue. Thanks! > > ### Is your feature request related to a problem? > * See [[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](https://github.com/actions/runner-images/issues/13474) . > > ### Describe the feature you would like. > * * I personally believe it's necessary to support native tests running the master branch on either Docker Engine v28 or Docker Engine v29. Currently, in the GitHub Actions CI files, the Ubuntu Runner uses Docker Engine v27, and the Windows Server Runner uses Rancher Desktop, which bundles Docker Engine v28.* Because the master branch is using `org.testcontainers:testcontainers-bom:2.0.1`, executing `./mvnw -PgenerateMetadata -e -T 1C clean verify` via Docker Engine v29 will not find the Docker environment, which is affected by [[Bug]: Docker 29.0.0 could not find a valid Docker environment testcontainers/testcontainers-java#11212](https://github.com/testcontainers/testcontainers-java/issues/11212) . On the other hand, the updated version `org.testcontainers:testcontainers-bom:2.0.3` only supports Docker Engine v29 and later, which conflicts with the default configuration of Rancher Desktop. See [[Bug]: Can't overwrite Docker socket path with 2.0.2 / Podman stopped working te stcontainers/testcontainers-java#11254](https://github.com/testcontainers/testcontainers-java/issues/11254) .* If we don't wait for [[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](https://github.com/actions/runner-images/issues/13474) to close, we need to perform an operation similar to `sudo tee /etc/docker/daemon.json` on all CIs involving test containers. We cannot remain at `"min-api-version": "1.24"` forever, as the related compatibility code will soon be removed by Docker Engine. See [daemon: raise default minimum API version to v1.44 moby/moby#51186](https://github.com/moby/moby/pull/51186) .* Therefore, the current direction for resolving this issue seems to be as follows:* [x] The documentation should be updated to require developers using Docker Engine v29 to perform the following actions: > > sudo tee /etc/docker/daemon.json <<EOF > { > "log-driver": "local", > "min-api-version": "1.24" > } > EOF > > sudo systemctl restart docker.service > * [x] After [[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](https://github.com/actions/runner-images/issues/13474) is closed, bump the testcontainers version to `2.0.3`.[ ] After [[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](https://github.com/actions/runner-images/issues/13474) is closed, update the documentation to require developers on Windows 11 to update the `/etc/docker/daemon.json` configuration for Rancher Desktop to use `min-api-version`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
