Docker Community Forums

Share and learn in the Docker community.

Get Started, Part 4: Swarms - Connection Refused


(Mmockus) #1

Issue Type: Connection refused
OS: Windows 10
Docker: 18.09.4

Follow the instructions per Get Started, Part 4: Swarms

The swarm successfully starts as demonstrated by

PS > docker-machine ls

ID                  NAME                  IMAGE                       NODE                DESIRED STATE       CURRENT STATE           ERROR               PORTS
btgnueafley1        getstartedlab_web.1   mmockus/get-started:part2   myvm1               Running             Running 4 minutes ago
a0rq76slzkoe        getstartedlab_web.2   mmockus/get-started:part2   myvm2               Running             Running 4 minutes ago
hyniqxvw3195        getstartedlab_web.3   mmockus/get-started:part2   myvm2               Running             Running 4 minutes ago
wuh21bntzrk3        getstartedlab_web.4   mmockus/get-started:part2   myvm1               Running             Running 4 minutes ago
wnykbu0ohk7l        getstartedlab_web.5   mmockus/get-started:part2   myvm2               Running             Running 4 minutes ago
PS> docker-machine ls
NAME    ACTIVE   DRIVER   STATE     URL                        SWARM   DOCKER     ERRORS
myvm1   *        hyperv   Running   tcp://192.168.1.252:2376           v18.09.0
myvm2   -        hyperv   Running   tcp://192.168.1.125:2376           v18.09.0

But when I attempt to connect to either host I get a connection refused from either the browser or curl command

Browser

This site can’t be reached 192.168.1.252 refused to connect.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED

CURL

C:>  curl http://192.168.1.252
curl: (7) Failed to connect to 192.168.1.252 port 80: Connection refused

(Vmtornikoski) #2

I’m having the same issue. VMs can ping each other, but curl is refused between them. VMs can ping and curl google.com.


(Rasoh) #3

I had the same issue. Solution is here: https://github.com/docker/machine/issues/4608


(Mmockus) #4

Confirmed switching to the older boot2docker.iso does fix this issue. Thanks for helping me find it.