Fix a few spelling mistakes in the docs
This commit is contained in:
@ -54,7 +54,7 @@ This supplies a configuration parameter to the bridge plugin -- the created brid
|
|||||||
Notice that `mtu` has also been specified and this value will not be overwritten by flannel plugin.
|
Notice that `mtu` has also been specified and this value will not be overwritten by flannel plugin.
|
||||||
|
|
||||||
Additionally, the `delegate` field can be used to select a different kind of plugin altogether.
|
Additionally, the `delegate` field can be used to select a different kind of plugin altogether.
|
||||||
To use `ipvlan` instead of `bridge`, the following configuratoin can be specified:
|
To use `ipvlan` instead of `bridge`, the following configuration can be specified:
|
||||||
|
|
||||||
```
|
```
|
||||||
{
|
{
|
||||||
|
@ -4,7 +4,7 @@
|
|||||||
|
|
||||||
[macvlan](http://backreference.org/2014/03/20/some-notes-on-macvlanmacvtap/) functions like a switch that is already connected to the host interface.
|
[macvlan](http://backreference.org/2014/03/20/some-notes-on-macvlanmacvtap/) functions like a switch that is already connected to the host interface.
|
||||||
A host interface gets "enslaved" with the virtual interfaces sharing the physical device but having distinct MAC addresses.
|
A host interface gets "enslaved" with the virtual interfaces sharing the physical device but having distinct MAC addresses.
|
||||||
Since each macvlan interface has its own MAC address, it makes it easy to use with exising DHCP servers already present on the network.
|
Since each macvlan interface has its own MAC address, it makes it easy to use with existing DHCP servers already present on the network.
|
||||||
|
|
||||||
## Example configuration
|
## Example configuration
|
||||||
|
|
||||||
|
2
ptp.md
2
ptp.md
@ -6,7 +6,7 @@ One end of the veth pair is placed inside a container and the other end resides
|
|||||||
Both ends receive an IP address out of a /31 range.
|
Both ends receive an IP address out of a /31 range.
|
||||||
The IP of the host end becomes the gateway address inside the container.
|
The IP of the host end becomes the gateway address inside the container.
|
||||||
|
|
||||||
Because ptp plugin requires a pair of IP addresses for each container, it should be used in conjuction with host-local-ptp IPAM plugin.
|
Because ptp plugin requires a pair of IP addresses for each container, it should be used in conjunction with host-local-ptp IPAM plugin.
|
||||||
|
|
||||||
## Example network configuration
|
## Example network configuration
|
||||||
```
|
```
|
||||||
|
Reference in New Issue
Block a user