Files
podman/libpod
Aditya R 06241077cc libpod,netavark: correctly populate /etc/resolv.conf with custom dns server
After https://github.com/containers/netavark/pull/452 `netavark` is
incharge of deciding `custom_dns_servers` if any so lets honor that and
libpod should not set these manually.

This also ensures docker parity
Podman populates container's `/etc/resolv.conf` with custom DNS servers ( specified via `--dns` or `dns_server` in containers.conf )
even when container is connected to a network where `dns_enabled` is `true`.

Current behavior does not matches with docker, hence following commit ensures that podman only populates custom DNS server when container is not connected to any network where DNS is enabled and for the cases where `dns_enabled` is `true`
the resolution for custom DNS server will happen via ( `aardvark-dns` or `dnsname` ).

Reference: https://docs.docker.com/config/containers/container-networking/#dns-services
Closes: containers#16172

Signed-off-by: Aditya R <arajan@redhat.com>
2023-01-22 12:48:55 +05:30
..
2022-01-18 12:47:07 +01:00
2017-11-01 11:24:59 -04:00
2022-12-15 13:39:56 +01:00
2022-10-17 09:19:41 +02:00
2022-01-18 12:47:07 +01:00
2022-09-20 15:34:27 -04:00
2022-09-10 07:52:00 -04:00
2022-09-10 07:52:00 -04:00
2022-09-10 07:52:00 -04:00
2022-04-25 13:23:20 +02:00
2022-09-01 13:02:01 -04:00
2022-10-17 09:19:41 +02:00
2022-12-15 13:39:56 +01:00
2022-01-18 12:47:07 +01:00
2022-07-21 14:50:01 -04:00
2022-09-20 15:34:27 -04:00
2022-09-10 07:52:00 -04:00
2022-09-20 15:34:27 -04:00
2022-09-10 07:52:00 -04:00
2022-01-18 12:47:07 +01:00