Open brysontyrrell opened 7 years ago
I am also having this issue on version docker-machine version 0.12.2, build 9371605
, it appears to happen right after I create a multi node env. Driver = vmwarevsphere
Could this be related to that fact that the default timeout is set to low? lsDefaultTimeout = 10
My command always seems to error out after 10 seconds, in larger environments I could see this taking longer that 10 seconds.
same error after I created the 3rd node
# docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
docker01 vmwarevsphere Timeout
docker02 vmwarevsphere Timeout
docker03 vmwarevsphere Timeout
Error attempting call to get driver name: connection is shut down
Error attempting call to get driver name: connection is shut down
# docker-machine version
docker-machine version 0.12.2, build 9371605
I was able to get rid of these error by removing the references to remote instances that no longer exist using docker-machine rm <instance name>.
Once I did that, docker-machine ls
returned the list of available nodes without any errors
I was able to get rid of these error by removing the references to remote instances that no longer exist using
docker-machine rm <instance name>.
Once I did that,docker-machine ls
returned the list of available nodes without any errors
This worke for me as well
docker-machine version 0.11.0, build 5b27455
I have a number of remote hosts that I need to enable VPN to access. After updating to the latest version of Docker Toolkit I'm now getting extra errors when below the host list for those that are in a timeout state.
The errors do not appear when when
docker-machine
is able to reach all hosts.