1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
moby--moby/libnetwork/drivers
Jana Radhakrishnan 524b3dca97 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
..
bridge Remove dependency on libcontainer 2015-07-16 13:26:26 -07:00
host Honor driver side resolv.conf file 2015-07-02 10:39:06 -07:00
null Replacing isReservedNetwork with Driver capability 2015-06-10 23:59:38 -07:00
overlay Sometimes fdb points to wrong vtep 2015-07-20 18:01:40 -07:00
remote Replacing isReservedNetwork with Driver capability 2015-06-10 23:59:38 -07:00
windows Replacing isReservedNetwork with Driver capability 2015-06-10 23:59:38 -07:00