docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #282 from mstanleyjones/add_macvlan_to_toc 

Add get-started-macvlan.md to TOC
This commit is contained in:
John Mulhausen 2016-10-19 22:51:38 -07:00 committed by GitHub
parent 5c511ac085 9c1de966a7
commit 60c9df35d9
2 changed files with 8 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_data/toc.yaml
View File

@ -111,6 +111,8 @@ toc:
title: Work with network commands title: Work with network commands
- path: /engine/userguide/networking/get-started-overlay/ - path: /engine/userguide/networking/get-started-overlay/
title: Get started with multi-host networking title: Get started with multi-host networking
- path: /engine/userguide/networking/get-started-macvlan/
title: Get started with macvlan network driver
- path: /engine/userguide/networking/overlay-security-model/ - path: /engine/userguide/networking/overlay-security-model/
title: Swarm mode overlay network security model title: Swarm mode overlay network security model
- path: /engine/userguide/networking/configure-dns/ - path: /engine/userguide/networking/configure-dns/

16
engine/userguide/networking/get-started-macvlan.md
View File

@ -2,10 +2,6 @@
description: Use macvlan for container networking description: Use macvlan for container networking
keywords: keywords:
- Examples, Usage, network, docker, documentation, user guide, macvlan, cluster - Examples, Usage, network, docker, documentation, user guide, macvlan, cluster
menu:
main:
parent: smn_networking
weight: -3
title: Get started with macvlan network driver title: Get started with macvlan network driver
--- ---
@ -26,7 +22,7 @@ Macvlan offers a number of unique features and plenty of room for further innova
- All of the examples can be performed on a single host running Docker. Any examples using a sub-interface like `eth0.10` can be replaced with `eth0` or any other valid parent interface on the Docker host. Sub-interfaces with a `.` are created on the fly. `-o parent` interfaces can also be left out of the `docker network create` all together and the driver will create a `dummy` interface that will enable local host connectivity to perform the examples. - All of the examples can be performed on a single host running Docker. Any examples using a sub-interface like `eth0.10` can be replaced with `eth0` or any other valid parent interface on the Docker host. Sub-interfaces with a `.` are created on the fly. `-o parent` interfaces can also be left out of the `docker network create` all together and the driver will create a `dummy` interface that will enable local host connectivity to perform the examples.
- Kernel requirements: - Kernel requirements:
- To check your current kernel version, use `uname -r` to display your kernel version - To check your current kernel version, use `uname -r` to display your kernel version
- Macvlan Linux kernel v3.9–3.19 and 4.0+ - Macvlan Linux kernel v3.9–3.19 and 4.0+
@ -36,13 +32,13 @@ Macvlan Bridge mode has a unique MAC address per container used to track MAC to
- Macvlan driver networks are attached to a parent Docker host interface. Examples are a physical interface such as `eth0`, a sub-interface for 802.1q VLAN tagging like `eth0.10` (`.10` representing VLAN `10`) or even bonded host adaptors which bundle two Ethernet interfaces into a single logical interface. - Macvlan driver networks are attached to a parent Docker host interface. Examples are a physical interface such as `eth0`, a sub-interface for 802.1q VLAN tagging like `eth0.10` (`.10` representing VLAN `10`) or even bonded host adaptors which bundle two Ethernet interfaces into a single logical interface.
- The specified gateway is external to the host provided by the network infrastructure. - The specified gateway is external to the host provided by the network infrastructure.
- Each Macvlan Bridge mode Docker network is isolated from one another and there can be only one network attached to a parent interface at a time. There is a theoretical limit of 4,094 sub-interfaces per host adaptor that a Docker network could be attached to. - Each Macvlan Bridge mode Docker network is isolated from one another and there can be only one network attached to a parent interface at a time. There is a theoretical limit of 4,094 sub-interfaces per host adaptor that a Docker network could be attached to.
- Any container inside the same subnet can talk to any other container in the same network without a gateway in `macvlan bridge`. - Any container inside the same subnet can talk to any other container in the same network without a gateway in `macvlan bridge`.
- The same `docker network` commands apply to the vlan drivers. - The same `docker network` commands apply to the vlan drivers.
- In Macvlan mode, containers on separate networks cannot reach one another without an external process routing between the two networks/subnets. This also applies to multiple subnets within the same `docker network - In Macvlan mode, containers on separate networks cannot reach one another without an external process routing between the two networks/subnets. This also applies to multiple subnets within the same `docker network
@ -83,14 +79,14 @@ ping -c 4 172.16.86.10
``` ```
Take a look at the containers ip and routing table: Take a look at the containers ip and routing table:
``` ```
ip a show eth0 ip a show eth0
eth0@if3: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UNKNOWN eth0@if3: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UNKNOWN
link/ether 46:b2:6b:26:2f:69 brd ff:ff:ff:ff:ff:ff link/ether 46:b2:6b:26:2f:69 brd ff:ff:ff:ff:ff:ff
inet 172.16.86.2/24 scope global eth0 inet 172.16.86.2/24 scope global eth0
ip route ip route
default via 172.16.86.1 dev eth0 default via 172.16.86.1 dev eth0
172.16.86.0/24 dev eth0 src 172.16.86.2 172.16.86.0/24 dev eth0 src 172.16.86.2
@ -176,7 +172,7 @@ docker run --net=macvlan50 -it --name macvlan_test6 --rm alpine /bin/sh
In the second network, tagged and isolated by the Docker host, `eth0.60` is the parent interface tagged with vlan id `60` specified with `-o parent=eth0.60`. The `macvlan_mode=` defaults to `macvlan_mode=bridge`. It can also be explicitly set with the same result as shown in the next example. In the second network, tagged and isolated by the Docker host, `eth0.60` is the parent interface tagged with vlan id `60` specified with `-o parent=eth0.60`. The `macvlan_mode=` defaults to `macvlan_mode=bridge`. It can also be explicitly set with the same result as shown in the next example.
``` ```
# now add networks and hosts as you would normally by attaching to the master (sub)interface that is tagged. # now add networks and hosts as you would normally by attaching to the master (sub)interface that is tagged.
docker network create -d macvlan \ docker network create -d macvlan \
--subnet=192.168.60.0/24 \ --subnet=192.168.60.0/24 \
--gateway=192.168.60.1 \ --gateway=192.168.60.1 \