You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
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 :-)
The text was updated successfully, but these errors were encountered:
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.
Configuration :
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 :
Same issue here :
I haven't found the proxy configuration for the docker client, only for docker engine.
No problem for ssh :
Please, it's the last step to success :-)
The text was updated successfully, but these errors were encountered: