Steps to reproduce the issue:
- Init swarm (node a)
- Join 2 nodes (node b, node c)
- docker service create --name tomcat --publish 8180:8180 private-repo/tomcat
- Exec bash into the container
- curl -v tomcat:8180
-> Tries IP 10.255.0.6 (which is the VIP) -> fails, No route to host
- curl -v tasks.tomcat:8180
-> Tries IP 10.255.0.7 (which is the IP of the container) -> works.
Describe the results you received:
Can curl to the container IP from itself, but can't curl to the VIP
Additionally, if I start a new service on the same default network, and try to reach the container IP (tasks.tomcat) or the service VIP, neither work.
Describe the results you expected:
Should be able to curl to the VIP resolved by DNS...
Additional information you deem important (e.g. issue happens only occasionally):
100% reproducible. What am I missing?
Steps to reproduce the issue:
-> Tries IP 10.255.0.6 (which is the VIP) -> fails, No route to host
-> Tries IP 10.255.0.7 (which is the IP of the container) -> works.
Describe the results you received:
Can curl to the container IP from itself, but can't curl to the VIP
Additionally, if I start a new service on the same default network, and try to reach the container IP (tasks.tomcat) or the service VIP, neither work.
Describe the results you expected:
Should be able to curl to the VIP resolved by DNS...
Additional information you deem important (e.g. issue happens only occasionally):
100% reproducible. What am I missing?