dybyte opened a new pull request, #10495:
URL: https://github.com/apache/seatunnel/pull/10495
### Purpose of this pull request
The current CI process is consistently failing with the following error.
```
[testcontainers-lifecycle-0] ERROR
org.testcontainers.dockerclient.DockerClientProviderStrategy - Could not find a
valid Docker environment. Please check configuration. Attempted configurations
were:
UnixSocketClientProviderStrategy: failed with exception
BadRequestException (Status 400: {"message":"client version 1.32 is too old.
Minimum supported API version is 1.44, please upgrade your client to a newer
version"}
```
For more detailed information regarding this issue, please refer to
https://github.com/testcontainers/testcontainers-java/issues/11491 .
### Does this PR introduce _any_ user-facing change?
No.
### How was this patch tested?
### Check list
* [ ] If any new Jar binary package adding in your PR, please add License
Notice according
[New License
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/contribution/new-license.md)
* [ ] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [ ] If necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR.
* [ ] If you are contributing the connector code, please check that the
following files are updated:
1. Update
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
and add new connector information in it
2. Update the pom file of
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
3. Add ci label in
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
4. Add e2e testcase in
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
5. Update connector
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
--
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]
