Comment 3 for bug 1718548

I could not see the docker failure when running a local ADT test. So I added the checking with some additional output to see what is going on. The latest test failure (at least now it is detected quickly) http://autopkgtest.ubuntu.com/packages/u/ubuntu-fan/artful/amd64 shows that the host side is ok (using systemd-resolve --status on the first default route found returns a sensible forwarder). Also the fact that the image can be downloaded hints that the host side is good. And the LXD test is using the same setup (also the same underlay of 10.220.0.0/16) and works.

The difference is that LXD is using the dnsmasq based resolver which the fan tools set up, while docker is using its own (127.0.0.11) service. Not sure what the exact environment setup in ADT testing is, but could docker be affected by the same multiple default route issue which we had with the LXD tests? I don't think fanatic can do much as dns does not seem to be something one can influence with network create.