davedwwang opened a new issue, #4088:
URL: https://github.com/apache/amoro/issues/4088

   ### What happened?
   
   The integration tests (specifically AmoroAMSTest) are failing in the GitHub 
Actions environment. The error log indicates that Testcontainers is attempting 
to use Docker API version 1.32, which is no longer supported by the Docker 
daemon in the current GitHub Runner environment. The runner now requires a 
minimum API version of 1.44.
   
   ### Affects Versions
   
   master
   
   ### What table formats are you seeing the problem on?
   
   _No response_
   
   ### What engines are you seeing the problem on?
   
   _No response_
   
   ### How to reproduce
   
   _No response_
   
   ### Relevant log output
   
   ```shell
   15:39:14.875 INFO org.apache.amoro.server.AmoroServiceContainer: Starting 
AMS standalone containers...
   15:39:15.577 ERROR 
org.testcontainers.dockerclient.DockerClientProviderStrategy: Could not find a 
valid Docker environment. Please check configuration. Attempted configurations 
were:
   15:39:15.577 ERROR 
org.testcontainers.dockerclient.DockerClientProviderStrategy:     
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"}
   )
   15:39:15.577 ERROR 
org.testcontainers.dockerclient.DockerClientProviderStrategy: As no valid 
configuration was found, execution cannot continue
   Error:  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
0.799 s <<< FAILURE! - in org.apache.amoro.server.AmoroAMSTest
   ```
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's Code of Conduct


-- 
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]

Reply via email to