You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over time, ingress requests on our Swarm cluster start timing out when one host node tries to route traffic to a container on another host node. We've found that the ingress-sbox container on the ingress network on those 2 hosts have the same private ip address.
Steps to reproduce the issue:
Run a swarm with multiple managers on a self-updating, self-rebooting OS (Container Linux)
Wait
Observe intermidden timeouts
Describe the results you received:
If the container that's suppose to handle ingress traffic is in global mode, for example, and constrained to only the manager nodes (ie there are 3 containers spread across 3 host nodes), 1 out of 3 ingress requests to the external address of one of the manager host nodes times out.
Describe the results you expected:
Perfect routing.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
Version: 17.12.1-ce
API version: 1.35
Go version: go1.9.4
Git commit: 7390fc6
Built: Tue Feb 27 22:10:31 2018
OS/Arch: linux/amd64
Server:
Engine:
Version: 17.12.1-ce
API version: 1.35 (minimum version 1.12)
Go version: go1.9.4
Git commit: 7390fc6
Built: Tue Feb 27 22:10:31 2018
OS/Arch: linux/amd64
Experimental: true
I haven't seen a particular signature of duplicate IP addresses on the ingress networks. However, there were definitely general duplicate IP address issues fixed in the 18.03 CE release. See moby/libnetwork#2105 in particular.
Over time, ingress requests on our Swarm cluster start timing out when one host node tries to route traffic to a container on another host node. We've found that the
ingress-sbox
container on theingress
network on those 2 hosts have the same private ip address.Steps to reproduce the issue:
Describe the results you received:
If the container that's suppose to handle ingress traffic is in global mode, for example, and constrained to only the manager nodes (ie there are 3 containers spread across 3 host nodes), 1 out of 3 ingress requests to the external address of one of the manager host nodes times out.
Describe the results you expected:
Perfect routing.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:nodeA
nodeB
nodeC
Additional environment details (AWS, VirtualBox, physical, etc.):
AWS across 3 AZs using CoreOS Container Linux AMIs and identical Launch Configurations.
This is a duplicate and simplified explanation of #36871.
The text was updated successfully, but these errors were encountered: