connect to x.x.x.1 port 8000: Connection refused
summerQLin opened this issue · comments
Hi,
Thanks for this great job!
I am trying the demo 'whoami', and haproxy works fine. I was able to see backend container id.
But when I deployed my own services on one backend server x.x.x.2
- Container
2600516615c7
from Imageservice1
exposed port0.0.0.0:8080->5001/tcp
- Container
a6fc817cbca3
from Imageservice2
exposed port0.0.0.0:443->5000/tcp
Same containers are running on another backend server x.x.x.3 - Container
814d49616255
from Imageservice1
exposed port0.0.0.0:8080->5001/tcp
- Container
31eb936f2e59
from Imageservice1
exposed port0.0.0.0:8080->5001/tcp
docker-discover is deployed on server x.x.x.1
But when call service1 api from address x.x.x.1:8080, I got
connect to x.x.x.1 port 8080: Connection refused
I curl etcd for key 'backends/service1', it showed me 3 sub nodes 'backends/service1/2600516615c7',
'backends/service2/814d49616255', 'backends/service1/port'
And for haproxy config, I see
listen service1
bind *:5001
server 814d49616255 x.x.x.2:8080 check inter 2s rise 3 fall 2
server 2600516615c7 x.x.x.3:8080 check inter 2s rise 3 fall 2