Jesse Pretorius f11bbc4f34 Make the LXC cache prep use the host resolver config ... Currently the container cache preparation process uses a list of resolver addresses in order to prepare the container DNS resolution configuration. This presents a few problems: - The default value is set to Google's DNS addresses, which may not be accessible from a deployer's environment. This will cause an installation to fail and the deployer will have to dig around to find out why. This is counterintuitive - it would be better if the default process was to discover the host's configuration and to use that instead. - Nothing other than a very simple resolv.conf can be implemented. Deployers may wish to implement more advanced settings such as timeouts and round-robin queries. This patch changes the image cache preparation process to ensure that the container resolver configuration matches that of the host. This is simpler and more intuitive. Change-Id: I66b448dee361e231d172eb278b290ec4dccfdf97		2016-05-27 16:21:07 +00:00
..
redhat-7.yml	Make the LXC cache prep use the host resolver config	2016-05-27 16:21:07 +00:00
ubuntu-14.04.yml	Make the LXC cache prep use the host resolver config	2016-05-27 16:21:07 +00:00
ubuntu-16.04.yml	Make the LXC cache prep use the host resolver config	2016-05-27 16:21:07 +00:00