Closed titpetric closed 7 years ago
Looks like a duplicate of #28492
@titpetric Could you try with 127.0.0.1
instead? We think localhost
resolves to ::1
and this is an IPv6 issue.
/cc @sanimej @mavenugo
Dispatching to @mavenugo for routing
@aluzzardi I have already this info in the original report. It is a duplicate, it seems it affects docker from 1.12, 1.13 up to 17.03, If you'd like to adjust the labels on that report and close this one I am fine with that.
Thanks @titpetric. Yes. lets close this in favor of #28492 and adjust the labels.
Description
I'm trying to run a simple docker swarm service, exposing it with
-p 80:80
. The service responds on the LAN IP (eth0), but does not respond on localhost (even if connection is established).Steps to reproduce the issue:
docker service create --replicas 5 --network party-swarm --update-parallelism 5 --name sonyflake -p 80:80 titpetric/sonyflake
Describe the results you received:
Describe the results you expected:
I expected that
telnet localhost 80
will respond as it does with others.Additional information you deem important (e.g. issue happens only occasionally):
Actually, it seems to be related to ipv6, because this:
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
Hyper-V VM, 3 node swarm, running on leader: