more fundamentals CNM tweaks

This commit is contained in:
Bret Fisher
2018-05-03 19:28:39 -04:00
parent 29e37c8e2b
commit a30eabc23a
3 changed files with 23 additions and 3 deletions

BIN
slides/images/bridge1.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

BIN
slides/images/bridge2.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

View File

@@ -75,6 +75,8 @@ eb0eeab782f4 host host
---
class: extra-details
## Differences with the CNI
* CNI = Container Network Interface
@@ -87,6 +89,22 @@ eb0eeab782f4 host host
---
class: pic
## Single container in a Docker network
![bridge0](images/bridge1.png)
---
class: pic
## Two containers on two Docker networks
![bridge3](images/bridge2.png)
---
## Creating a network
Let's create a network called `dev`.
@@ -284,7 +302,7 @@ since we wiped out the old Redis container).
---
class: x-extra-details
class: extra-details
## Names are *local* to each network
@@ -472,11 +490,13 @@ b2887adeb5578a01fd9c55c435cad56bbbe802350711d2743691f95743680b09
* If containers span multiple hosts, we need an *overlay* network to connect them together.
* Docker ships with a default network plugin, `overlay`, implementing an overlay network leveraging VXLAN.
* Docker ships with a default network plugin, `overlay`, implementing an overlay network leveraging
VXLAN, *enabled with Swarm Mode*.
* Other plugins (Weave, Calico...) can provide overlay networks as well.
* Once you have an overlay network, *all the features that we've used in this chapter work identically.*
* Once you have an overlay network, *all the features that we've used in this chapter work identically
across multiple hosts.*
---