Docker Community Forums

Share and learn in the Docker community.

Access nginx (80) in browser after deploy in swarm


(Frans Thamura) #1

I have swarm-master, and 2 swarm node (swarm1, swarm2)

I deploy nginx with port 80 inside swarm-master, and run well, i can see both nginx in swarm1 and swarm2

but

when i try to access from 192.168.99.102, got this 192.168.99.102 refused to connect.

both using virtualbox

is there a missing setting in my side?

Ref: https://www.safaribooksonline.com/blog/2015/11/17/fun-with-docker-swarm/


(Jeff Anderson) #2

swarm doesn’t make the IP addresses of all swarm members somehow map to all containers. This is by design, as you might need to run two services that expose port 80. I would expect that you will be able to access a published port over the IP address of the host that is acting as the exit node for the network the container is attached to.


(Frans Thamura) #3

what happen if i run

docker run -d nginx

inside swarm-master? why swarm1 and swarm2 dont have daemon of nginx in both side?

I try both

docker run -d -e constraint:node==swarm1 nginx

docker run -d -e constraint:node==swarm1 --net=host --volume=/var/run/docker.sock:/tmp/docker.sock gliderlabs/registrator:latest consul://192.168.99.100:8500/

i cant get any change in my swarm?

can help?


(Dvohra) #4

Docker Swarm, a cluster manager for Docker hosts exposes a pool of hosts as a single “virtual” host. What is 192.168.99.102?