Docker-machine aws calls timing out

Docker Hub
1

I have been using docker-machine to create and manage aws nodes in a Docker swarm on my Dell laptop.

docker-machine create --driver amazonec2 --amazonec2-region ap-southeast-2 --amazonec2-subnet-id={subnet-id} --amazonec2-vpc-id={vc-id} aws-node-1

It was working perfectly, but at some point during the day it just stopped working and now every attempt to use docker-machine times out. I can’t use any command at all.

docker-machine ls -t 30
NAME         ACTIVE   DRIVER      STATE     URL   SWARM   DOCKER   ERRORS
aws-node-1            amazonec2   Timeout
aws-node-2            amazonec2   Timeout
aws-node-3            amazonec2   Timeout
aws-node-4            amazonec2   Timeout
aws-node-5            amazonec2   Timeout
Error attempting call to get driver name: connection is shut down
Error attempting call to get driver name: connection is shut down
Error attempting call to get driver name: connection is shut down

I have the latest version of docker-machine. Now I can’t even delete my local machine references because the rm command wants to synchronise with the remote nodes and can’t.

This is the command I use to establish my aws environmental variables, but of course this isn’t working either:

eval $(docker-machine env aws-node-1)

 Error checking TLS connection: RequestError: send request failed
 caused by: Post https://ec2.ap-southeast-2.amazonaws.com/: dial tcp: lookup ec2.ap-southeast- 2.amazonaws.com on 172.23.112.1:53: read udp 172.23.117.39:40246->172.23.112.1:53: i/o timeout

I’ve checked firewall settings and network connectivity, but I haven’t changed anything so it’s hard to know what to look for. It just stopped working. I can only think for some reason aws is blocking me.

Can anyone suggest anything? i can delete the ec2 nodes manually via the console, but I don’t know what to do about the local machine references.