mirror of https://github.com/docker/docs.git
chore: add missing IPvlan in network drivers list
Signed-off-by: Francisco Robles Martín f.robles.martin@pm.me
This commit is contained in:
parent
d336662dcb
commit
d2673f7458
|
|
@ -52,6 +52,11 @@ exist by default, and provide core networking functionality:
|
||||||
This strategy removes the need to do OS-level routing between these
|
This strategy removes the need to do OS-level routing between these
|
||||||
containers. See [overlay networks](overlay.md).
|
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,
|
- `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
|
making it appear as a physical device on your network. The Docker daemon
|
||||||
routes traffic to containers by their MAC addresses. Using the `macvlan`
|
routes traffic to containers by their MAC addresses. Using the `macvlan`
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue