Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

Proxy configuration for docker daemon tcp protocol #4394

Open
ClementB-OBS opened this issue Feb 12, 2018 · 1 comment
Open

Proxy configuration for docker daemon tcp protocol #4394

ClementB-OBS opened this issue Feb 12, 2018 · 1 comment

Comments

@ClementB-OBS
Copy link

ClementB-OBS commented Feb 12, 2018

Configuration :

  • docker-machine.exe version 0.13.0, build 9ba6da9
  • docker-client 18.01.0-ce
  • OS Windows 7 under Corporate Proxy (HTTP)

I tried to install and use a docker machine on OpenStack Provider.
No problem for machine creation and installation (I have set HTTP_PROXY and HTTPS_PROXY env variables for HTTP request, and configure ssh), but at the end :

Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "84.39.36.195:2376": dial tcp 84.39.36.195:2376: i/o timeout

Same issue here :

$ docker-machine ls
NAME      ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER        ERRORS
default   *        virtualbox   Running   tcp://192.168.99.100:2376           v18.02.0-ce
testing            openstack    Timeout

I haven't found the proxy configuration for the docker client, only for docker engine.

No problem for ssh :

$ docker-machine ssh testing

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
cloud@testing:~$

Please, it's the last step to success :-)

@volkc-basf
Copy link

Hi @ClementB-OBS,

we have a very similar problem with amazonec2 in our corporate network. I'm pretty sure that this is a bug of the dockerclient used by docker-machine. It simply ignores the proxy parameters that are set within the environment.

I've spent some time on writing a fix, samalba/dockerclient#245 should solve the issue.

Best,
Chris

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants