From d2673f7458aa07a3b897a8eed141211cb9ebf866 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Francisco=20Robles=20Mart=C3=ADn?= Date: Sun, 7 Nov 2021 16:29:58 +0100 Subject: [PATCH] chore: add missing IPvlan in network drivers list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Francisco Robles Martín f.robles.martin@pm.me --- network/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/network/index.md b/network/index.md index 37da95a7ae..c578d66dcd 100644 --- a/network/index.md +++ b/network/index.md @@ -52,6 +52,11 @@ exist by default, and provide core networking functionality: This strategy removes the need to do OS-level routing between these containers. See [overlay networks](overlay.md). +- `ipvlan`: IPvlan networks give users total control over both IPv4 and IPv6 + addressing. The VLAN driver builds on top of that in giving operators complete + control of layer 2 VLAN tagging and even IPvlan L3 routing for users + interested in underlay network integration. See [IPvlan networks](ipvlan.md). + - `macvlan`: Macvlan networks allow you to assign a MAC address to a container, making it appear as a physical device on your network. The Docker daemon routes traffic to containers by their MAC addresses. Using the `macvlan`