Alessandro Boch

@tgraf Thanks for the change and help, we indeed need help to fill in some ipv6 missing parts in libnetwork. Put few comments. In summary, I think we should not...

@tgraf Thanks for the clarification. I am not sure about the option 2 you mentioned. Considering the behavior would be controlled by a user specified option, how would it be...

@tgraf Sorry for the back and forth. Looking at your new diffs, I am wondering whether it would be better to follow the approach you are using for request address...

@vasily-kirichenko > So my questing is: is my assumption valid that services should be discoverable across entire Swarm? I mean, name of a service should be DNS resolvable from any...

@zen-chetan > My intention in showing the host's /etc/resolv.conf was to demonstrate that the host and the name server it uses does not seem to overlap the docker overlay network's...

@brugnara This is expected. You told the ipam driver to reserve the address `10.150.0.254` as you are using it for your network's gateway. Then you attempt to reserve the same...

> How can I avoid the reservation as you mentioned? You can't avoid it. On network creation libnetwork will request the ipam driver for an address for the network's gateway,...

Yes @thinkhard-j-park report looks a duplicate of #31066, I am assuming a manual docker run was attempted on that attachable network and failed the allocation. In @silveraid report instead, I...

@DreamerKMP @stv0g please feel free to open a pull request with your proposed fix

@corny Can you please have the fou related changes and the nl changes into two separate PRs