Bridge conflict detection was broken since it would check bridge ranges that use the null IPAM driver (e.g. this very plugin!). null specifies a subnet of 0.0.0.0/0, which would obviously pass any IP range check. Any network using null or a /0 mask will be skipped, and other docker-net-dhcp networks' bridges will be compared in addition.
If the user wants to re-use the same bridge across multiple networks (not really recommended) or for some reason the conflict detection is still wrong, the new ignore_conflicts option can be used.
Bridge conflict detection was broken since it would check bridge ranges that use the
nullIPAM driver (e.g. this very plugin!).nullspecifies a subnet of0.0.0.0/0, which would obviously pass any IP range check. Any network usingnullor a/0mask will be skipped, and otherdocker-net-dhcpnetworks' bridges will be compared in addition.If the user wants to re-use the same bridge across multiple networks (not really recommended) or for some reason the conflict detection is still wrong, the new
ignore_conflictsoption can be used.Fixes #18.