Phil Estes c59fff945d Fix bridge initialization for IPv6 if IPv4-only docker0 exists ...

This fixes the daemon's failure to start when setting --ipv6=true for
the first time without deleting `docker0` bridge from a prior use with
only IPv4 addressing.

The addition of the IPv6 bridge address is factored out into a separate
initialization routine which is called even if the bridge exists but no
IPv6 addresses are found.

Docker-DCO-1.1-Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com> (github: estesp)
Upstream-commit: 0c8d17b5c1a142bc09abe1105d985e76db6f225d
Component: engine

2015-01-27 23:54:26 -05:00

..

bridge

Fix bridge initialization for IPv6 if IPv4-only docker0 exists

2015-01-27 23:54:26 -05:00

ipallocator

Remove BridgeIP from ipallocation pool

2015-01-08 16:21:09 +01:00

portallocator

fixed the way of iterating over the range of map.

2014-11-04 13:46:53 +08:00

portmapper

Move per-container forward rules to DOCKER chain

2014-12-21 12:57:32 +10:00

network_test.go

Implementing IPv6 functionality for ipallocator

2014-10-02 00:25:02 +02:00

network.go

Rename runtime/* to daemon/*

2014-04-17 14:43:01 -07:00

utils.go

Fix bridge initialization for IPv6 if IPv4-only docker0 exists

2015-01-27 23:54:26 -05:00