Rob Murray d365702dbd No default nameservers for internal resolver ...

Don't fall-back to Google's DNS servers in a network that has an
internal resolver.

Now the default bridge uses the internal resolver, the only reason a
network started by the daemon should end up without any upstream
servers is if the host's resolv.conf doesn't list any.  In this case,
the '--dns' option can be used to explicitly configure nameservers
for a container if necessary.

(Note that buildkit's containers do not have an internal resolver, so
they will still set up Google's nameservers if the host has no
resolvers that can be used in the container's namespace.)

Signed-off-by: Rob Murray <rob.murray@docker.com>

2024-06-05 20:27:24 +01:00

..

caller

fix duplicate words (dupwords)

2024-03-07 10:57:03 +01:00

kvstore

libnet: Replace DeleteAtomic in retry loops with DeleteIdempotent

2024-02-22 08:22:09 +01:00

netiputil

libnet/i/defaultipam: introduce a linear allocator

2024-05-23 08:24:51 +02:00

resolvconf

No default nameservers for internal resolver

2024-06-05 20:27:24 +01:00

setmatrix

add //go:build directives to prevent downgrading to go1.16 language

2023-12-15 15:24:15 +01:00