"The container gets non-conflicting IPs"

Question

"The container gets non-conflicting IPs"

Closed this issue 8 years ago · 1 comments

The VM gets the original container IPs. The container gets non-conflicting IPs

You increase the subnet mask to have some additional non-conflicting IPs?
Could be conflicting with routed subnets (docker host or external)?

Answer 1 · 2016-10-07T06:34:30.000Z

Nor really, because the new IP is not routable outside the container.

Indeed, the "non confilcting IP" is used only for the sake of dnsmasq to serve IP to the VM. Not even the VM can ping its container host in most configurations.