Files
moby/libnetwork
Rob Murray c21fe3efa3 Forward DNS requests into --internal networks
A recent change to prevent containers only connected to --internal
networks from communicating with external DNS servers inadvertently
prevented the daemon's internal DNS server from forwarding requests
within an internal network to a containerised DNS server.

Relax the check, so that only requests that need to be forwarded
from the host's network namespace are dropped.

External DNS servers remain unreachable from the internal network.

Signed-off-by: Rob Murray <rob.murray@docker.com>
(cherry picked from commit 77a47dba3b)
Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
2024-05-14 15:17:56 +02:00
..
2024-03-07 10:57:03 +01:00
2024-04-15 14:51:20 +01:00
2023-08-17 16:48:09 +02:00
2024-03-07 10:57:03 +01:00
2024-03-01 16:59:28 +00:00
2021-06-01 23:48:32 +00:00
2018-06-22 16:10:22 -07:00
2018-06-22 16:10:22 -07:00
2023-05-29 03:28:35 +02:00
2024-04-16 18:57:28 +01:00
2024-04-16 18:57:28 +01:00
2024-04-16 18:57:28 +01:00
2024-02-29 23:27:00 +00:00

libnetwork - networking for containers

Libnetwork provides a native Go implementation for connecting containers

The goal of libnetwork is to deliver a robust Container Network Model that provides a consistent programming interface and the required network abstractions for applications.

Design

Please refer to the design for more information.

Using libnetwork

There are many networking solutions available to suit a broad range of use-cases. libnetwork uses a driver / plugin model to support all of these solutions while abstracting the complexity of the driver implementations by exposing a simple and consistent Network Model to users.

Contributing

Want to hack on libnetwork? Docker's contributions guidelines apply.

Code and documentation copyright 2015 Docker, inc. Code released under the Apache 2.0 license. Docs released under Creative commons.