Jana Radhakrishnan c7b0931862 Sometimes fdb points to wrong vtep ...

When you start a container after some other container has already
been started in the same network, the current container will have
an fdb which points to a wrong vtep to reach the already started
container. This makes the network connectivity to not work. The root
cause of the issue is because of golang does variable capture by
reference in closures and so we cannot use the return values from
range iterators directly. It needs to be copied to a locally scoped
variable and then use that copy as a capture variable in the closure.

Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>

2015-07-20 18:01:40 -07:00

..

joinleave.go

Overlay driver

2015-06-18 15:06:24 -07:00

ov_endpoint.go

Overlay driver

2015-06-18 15:06:24 -07:00

ov_network.go

Adjust overlay driver for netlink api change

2015-07-02 10:39:43 -07:00

ov_serf.go

Overlay driver

2015-06-18 15:06:24 -07:00

ov_utils.go

Use IANA assigned VXLAN port

2015-07-03 03:43:02 +01:00

overlay_test.go

Overlay driver

2015-06-18 15:06:24 -07:00

overlay.go

Use IANA assigned VXLAN port

2015-07-03 03:43:02 +01:00

peerdb.go

Sometimes fdb points to wrong vtep

2015-07-20 18:01:40 -07:00