yuqi1129 opened a new issue, #9990:
URL: https://github.com/apache/gravitino/issues/9990

   ### Version
   
   main branch
   
   ### Describe what's wrong
   
   According to the failure information in 
https://github.com/apache/gravitino/actions/runs/21971261163/job/63473143409?pr=9878,
 docker can't be triggered by test container and the log message are
   
   ```
   2026-02-13 01:41:52 INFO  [Test worker] DockerClientFactory:150 - 
Testcontainers version: 1.20.6
   2026-02-13 01:41:53 INFO  [Test worker] 
DockerMachineClientProviderStrategy:64 - docker-machine executable was not 
found on PATH 
([/opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/17.0.18-8/x64/bin, /snap/bin, 
/home/runner/.local/bin, /opt/pipx_bin, /home/runner/.cargo/bin, 
/home/runner/.config/composer/vendor/bin, /usr/local/.ghcup/bin, 
/home/runner/.dotnet/tools, /usr/local/sbin, /usr/local/bin, /usr/sbin, 
/usr/bin, /sbin, /bin, /usr/games, /usr/local/games, /snap/bin])
   2026-02-13 01:41:53 ERROR [Test worker] DockerClientProviderStrategy:266 - 
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"}
   )
        DockerDesktopClientProviderStrategy: failed with exception 
NullPointerException (Cannot invoke "java.nio.file.Path.toString()" because the 
return value of 
"org.testcontainers.dockerclient.DockerDesktopClientProviderStrategy.getSocketPath()"
 is null)As no valid configuration was found, execution cannot continue.
   See https://java.testcontainers.org/on_failure.html for more details.
   2026-02-13 01:41:54 INFO  [Test worker] DockerClientFactory:150 - 
Testcontainers version: 1.20.6
   2026-02-13 01:41:54 INFO  [Test worker] CommandExecutor:51 - Sending command 
"bash -c /home/runner/work/gravitino/gravitino/bin/gravitino.sh stop" to 
localhost
   2026-02-13 01:41:55 INFO  [Test worker] BaseIT:465 - Tearing down Gravitino 
Server
   2026-02-13 01:41:55 INFO  [Test worker] DockerClientFactory:150 - 
Testcontainers version: 1.20.6
   2026-02-13 01:41:55 INFO  [Test worker] CommandExecutor:51 - Sending command 
"bash -c /home/runner/work/gravitino/gravitino/bin/gravitino.sh stop" to 
localhost
   2026-02-13 01:41:56 INFO  [Test worker] BaseIT:465 - Tearing down Gravitino 
Server
   2026-02-13 01:41:56 INFO  [Test worker] DockerClientFactory:150 - 
Testcontainers version: 1.20.6
   2026-02-13 01:41:56 INFO  [Test worker] CommandExecutor:51 - Sending command 
"bash -c /home/runner/work/gravitino/gravitino/bin/gravitino.sh stop" to 
localhost
   2026-02-13 01:41:57 INFO  [Test worker] BaseIT:465 - Tearing down Gravitino 
Server
   2026-02-13 01:41:58 INFO  [Test worker] DockerClientFactory:150 - 
Testcontainers version: 1.20.6
   2026-02-13 01:41:58 INFO  [Test worker] CommandExecutor:51 - Sending command 
"bash -c /home/runner/work/gravitino/gravitino/bin/gravitino.sh stop" to 
localhost
   2026-02-13 01:41:59 INFO  [Test worker] BaseIT:465 - Tearing down Gravitino 
Server
   2026-02-13 01:41:59 INFO  [Test worker] DockerClientFactory:150 - 
Testcontainers version: 1.20.6
   2026-02-13 01:41:59 INFO  [Test worker] CommandExecutor:51 - Sending command 
"bash -c /home/runner/work/gravitino/gravitino/bin/gravitino.sh stop" to 
localhost
   2026-02-13 01:42:00 INFO  [Test worker] BaseIT:465 - Tearing down Gravitino 
Server
   ```
   
   Possibly, the problem is due to a low Docker client API, as we found that 
the runner image 
https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20260209.23 
has upgrade the docker version.  
   
   ### Error message and/or stacktrace
   
   Please see above.
   
   ### How to reproduce
   
   Please see above.
   
   ### Additional context
   
   We need to upgrade the version of test container.


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