Colin Walters 870eed9378 Use host's resolv.conf if no network namespace enabled ... My host system runs Fedora Silverblue 29 and I have NetworkManager's `dns=dnsmasq` setting enabled, so my `/etc/resolv.conf` only has `127.0.0.1`. I also run my development podman containers with `--net=host` for various reasons. If we have a host network namespace, there's no reason not to just use the host's nameserver configuration either. This fixes e.g. accessing content on a VPN, and is also faster since the container is using cached DNS. I know this doesn't solve the bigger picture issue of localhost-DNS conflicting with bridged networking, but that's far more involved, probably requiring a DNS proxy in the container. This patch makes my workflow a lot nicer and was easy to write. Signed-off-by: Colin Walters <walters@verbum.org>		2018-11-27 15:28:09 -05:00
..
dns	Drop libnetwork vendor and move the code into pkg/	2018-10-04 17:34:59 -04:00
resolvconf.go	Use host's resolv.conf if no network namespace enabled	2018-11-27 15:28:09 -05:00