diff options
| author | Colin Walters <walters@verbum.org> | 2018-11-21 09:30:03 -0500 |
|---|---|---|
| committer | Colin Walters <walters@verbum.org> | 2018-11-27 15:28:09 -0500 |
| commit | 870eed9378c025f3684aa8baf3db6de969da3c5d (patch) | |
| tree | 26bb1dcc44a8519973ab119e34985a91efc52542 /test/policy.json | |
| parent | 6df7409cb5a41c710164c42ed35e33b28f3f7214 (diff) | |
| download | podman-870eed9378c025f3684aa8baf3db6de969da3c5d.tar.gz podman-870eed9378c025f3684aa8baf3db6de969da3c5d.tar.bz2 podman-870eed9378c025f3684aa8baf3db6de969da3c5d.zip | |
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>
Diffstat (limited to 'test/policy.json')
0 files changed, 0 insertions, 0 deletions