9. Overlay Driver
• Creates a separate network namespace for every network
- Facilitates overlapping IP address space across networks
• Creates a Linux Bridge and VXLAN tunnels to every other discovered
host
• Creates a veth pair for each endpoint
- One end is attached to the bridge
- The other appears as eth0 inside the container
• Network namespace connected to host network using NAT
- Facilitates exiting the overlay network at every host(for external connectivity)
10.
11.
12. Networking in Single Host - Notes
◼3 local network by default: Null, Host, Bridge ( like as: Docker0 ) - you
cannot delete them
◼2 Network Drivers: Bridge & overlay (need a cluster management)
◼Can assign multiple network to a container
◼Legacy links: docker run --link is not supported within a user-defined
bridge network. (only support with Bridge and Docker0)
13. Networking in Multiple Host - Notes
Prerequisites:
◼the Docker hosts with a 3.16 kernel version or higher
◼Access to a key-value store. Docker supports Consul, Etcd, and
ZooKeeper (Distributed store) key-value stores.
◼A cluster of hosts with connectivity to the key-value store.
◼A properly configured Engine daemon on each host in the cluster.
14. Networking in Multiple Host - Notes
◼Additionally, containers connected to the multi-host network are
automatically connected to the docker_gwbridge network.
◼docker_gwbridge allows the containers to have external
connectivity outside of their cluster.
16. Persitent Storage - Notes
What is new in 1.9 ?
◼Made the volume feature better and easier
◼Intergrating with swarm (even works - just to try it)
◼More storage drivers from third party:
◼Flocker
◼Blockbridge, Ceph, ClusterHQ, EMC and Portworx
17. Persitent Storage - Notes
What is new in 1.9 ?
◼Made the volume feature better and easier
◼Intergrating with swarm (even works - just to try it)
◼More storage drivers from third party:
◼Flocker
◼Blockbridge, Ceph, ClusterHQ, EMC and Portworx
◼Good feature: data volume container