b9e27acabc
A check was added to the bridge driver to detect when it was called to create the default bridge nw whereas a stale default bridge already existed. In such case, the bridge driver was deleting the stale network before re-creating it. This check was introduced in docker/libnetwork@6b158eac6a to fix an issue related to newly introduced live-restore. However, since commit docker/docker@ecffb6d58c, the daemon doesn't even try to create default networks if there're active sandboxes (ie. due to live-restore). Thus, now it's impossible for the default bridge network to be stale and to exists when the driver's CreateNetwork() method is called. As such, the check introduced in the first commit mentioned above is dead code and can be safely removed. Signed-off-by: Albin Kerouanton <albinker@gmail.com> |
||
|---|---|---|
| .. | ||
| bridge | ||
| host | ||
| ipvlan | ||
| macvlan | ||
| null | ||
| overlay | ||
| remote | ||
| windows | ||