Files
moby/libnetwork
Rob Murray 558da63444 Jump to DOCKER-INGRESS from DOCKER-FORWARD
A jump to DOCKER-INGRESS chain is only created when Swarm needs
it. That's always after jumps to DOCKER-USER and DOCKER-FORWARD
have been inserted at the top of the FORWARD chain. The
DOCKER-INGRESS rule needs to be between those two other jumps.

Placing the jump to DOCKER-INGRESS at the top of the DOCKER-FORWARD
chain puts it in the right place, without needing to shuffle any
other rules around when it's added.

Signed-off-by: Rob Murray <rob.murray@docker.com>
2025-02-25 17:17:36 +00:00
..
2025-01-20 10:10:51 +01:00
2024-11-12 14:02:09 +01:00
2025-02-25 15:24:25 +00:00
2024-06-27 23:18:48 +02:00
2025-02-24 17:09:09 +00:00
2025-02-25 15:24:25 +00:00
2024-09-06 21:53:09 +10:00
2024-09-06 21:53:09 +10:00
2025-01-27 14:19:19 +01: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.