Windows + docker in vagrant, EnvironmentAndSystemPropertyClientProviderStrategy don't work

[bderancourt]

Hi,

My issue looks like similar than #291: my setup is testContainers on windows that I need to connect to a docker daemon inside a vagrant box with port 2300 forwarded.

I have 3 environment variables set ;
DOCKER_HOST=tcp://%COMPUTERNAME%:2300
DOCKER_CERT_PATH=C:\git_clones\acs-localdev\docker-cert (shared forder in vagrant box)
DOCKER_TLS_VERIFY=1

I tried with docker-java (3.1.2) and spotify docker-client (8.16.0) ant it works near out-of-the-box:

  public static void dockerClient() throws Exception {
    final DockerClient docker = DefaultDockerClient.fromEnv()
        .build();
    // Pull an image
    docker.pull("couchbase/server:enterprise-5.5.3");
    docker.close();
  }

  public static void dockerJava() throws Exception {
    com.github.dockerjava.api.DockerClient dockerClient = DockerClientBuilder.getInstance()
        .withDockerCmdExecFactory(new JerseyDockerCmdExecFactory())
        .build();
    List<Container> containers = dockerClient.listContainersCmd().exec();
    dockerClient.close();
  }

But I'm unable to make it work with testcontainers, all the provider strategies failed.
ping fails with a javax.net.ssl.SSLPeerUnverifiedException: Hostname xxx not verified

How can I bypass it ?

[kiview]

Just to get some context, why aren't you using docker-machine?

[bderancourt]

Because I have to use the stack given by the tools team of my company.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[stale]

This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case.

[alinbutura]

Is there a plan to merge this PR in the near future? I am facing the same error and I was wondering if I should wait for the new release.
Thank you!