mirror of
https://github.com/containers/podman
synced 2024-10-21 09:45:32 +00:00
870eed9378
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> |
||
|---|---|---|
| .. | ||
| annotations | ||
| apparmor | ||
| chrootuser | ||
| criu | ||
| ctime | ||
| firewall | ||
| hooks | ||
| inspect | ||
| kubeutils | ||
| logs | ||
| lookup | ||
| namespaces | ||
| netns | ||
| registrar | ||
| registries | ||
| resolvconf | ||
| rootless | ||
| secrets | ||
| spec | ||
| util | ||
| varlinkapi | ||