Files
moby/libnetwork
Rob Murray 81f6e087c1 Treat connected routes to unspecified addrs like default gws
In L3 modes, the ipvlan driver can't set up a default gateway with
a next hop address, because there's no L2 for it to resolve the
gateway IP into a MAC address.

Instead, it sets up a route to 0.0.0.0 or [::] that's connected to
the network's interface. The end result is the same - the container
has a default route.

So, don't set up routes to 0.0.0.0/:: when applying routes when an
endpoint joins a sandbox, set them up when the endpoint is selected
as the container's gateway. And, drop those routes when another
endpoint becomes the gateway.

Signed-off-by: Rob Murray <rob.murray@docker.com>
2025-01-06 15:24:23 +00:00
..
2024-09-06 21:53:09 +10:00
2024-09-06 21:53:09 +10:00
2024-11-12 14:02:09 +01:00
2024-09-06 21:53:09 +10:00
2024-11-11 18:19:04 +08:00
2024-11-28 10:05:40 +01:00
2024-06-27 23:18:48 +02:00
2021-06-01 23:48:32 +00:00
2024-09-06 21:53:09 +10:00
2024-09-06 21:53:09 +10:00
2024-09-06 21:53:09 +10:00
2024-09-06 21:53:09 +10:00
2024-06-27 23:18:48 +02:00
2024-09-06 21:53:09 +10:00
2024-11-12 14:02:09 +01: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.