Docker Networking
THE BASICS
About Me
 |
 |
 |
DevOps@RajeshKumar.XYZ
Docker Networking
Course Introduction
Docker For Sysadmins Linux Windows VMware
Related Course
To get you up and runing...
Docker and containers:the big picture
- Course Intro
- What are Containers
- What is Docker
- Preparing to Thrive in a Container World
- What Kind of Work Will Containers Do?
- Are Docker and Containers Ready for Production...
Getting Started with dockes
- Course Intro
- Insttaling Docker
- Working with Containers
- Swarm Mode and Microservices.
agenda
Big Picture Roadmaps
coming up ...
The CMN and Libnetwork
the three pillars of docker networking
cnm Vs cni
| Container network model | AKA | Container network interface |
| Docker | Speciality | Kubernetes |
| Docker,Inc. | Origin | CoreOS,Inc. |
cnm
Sandbox
A.k.a. namespace Isolated area of OS Contains full network stack
Endpoint
Network interface. E.g. ethO
Network
Connected endpoints
CNM →Libnetwork →drivers
CNM →
CNM →
Libnetwork→
Central place for all Docker networking logic. API. UX etc...
htt ps://github.com/docker/libnetwork
X-platform Pluggable
Written in Go/Golang Real-world implementation of CNM by Docker. Inc.A
drivers
Network-Specific Detail
- Overlay
- MACVLAN
- IPVLAN
- Bridge
CNM →Libnetwork →drivers
| Design/DNA | Control Plane & Management Plane | Data P/ane |
CNM →
Libnetwork →
Central place for all Docker networking logic. API. UX etc...
htt ps://github.com/docker/libnetwork
X-platform Pluggable
Written in Go/Golang Real-world implementation of CNM by Docker. Inc.A
drivers
Network-Specific Detail
- Overlay
- MACVLAN
- IPVLAN
- Bridge
"Local" = native
"Remote" =3rd party
CNM
Master plan/grand design
Libnetwork
De facto implementation of the CNM
drivers
Network-specific detail
Coming up...
The hands-on stuff!!!!!
use cases and drivers
agenda
single-host networking
With the bridge driver(Linux)
~nat driver (Windows)
single-host
single-host
single-host
single-host
coming up...
Multi-host overlay networking
Multi-host networking
With the Docker overlay driver
multi-host overlay
coming up...
Joining existing networks with the MACVLAN driver
participating in existing networks
With the Linux MACVLAN driver
Similar(ish) to "I2bridge" on windowsLinux MACVLAN
- Every container gets its own IP
- Every container getS its own MAC
windows i2bridge
- Every container gets its own IP
- All containers share a common MAC
coming up...
demo...
coming up...
Joining existing networks with the IPVLAN driver
participating in existing networks
Similar to Linux MACVLAN
But doesn't give containers their own MAC address.
With the Linux IPVLAN driver
Similar to windows I2bridge
More cloud friendly than MACVLAN(YMMV)
Special considerations when working DHCP
Containers cannot ping their host
demo...
ipvlan : quick summary
Similar to MACVLAN,but ...
Doesn't require promiscuous mode
Doesn't give every container a MAC
Might be a issue with some cloud platforms
Needs hints about the underlay
Get your IPAM right!
Newer than overlay,bridge,MACVLAN...
coming up...
Network Services!
Network Services
agenda
Service Discovery
Port-based Routing with the Routing Mesh
App-aware Routing with the HTTP Routing Mesh
Service Discovery
modern apps
Made up of multiple smaller Services
- Sometimes loads!!
modern apps
Made up of multiple smaller Services
- Sometimes loads!!
"Microservices"
modern apps
Made up of multiple smaller Services
- Sometimes loads!!
"Microservices"
Service Discovery is massively important
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
Made up of multiple smaller Services
- Sometimes loads!!
"Microservices"
Service Discovery is massively important
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
DNS Service Discovery in Docker
Made up of multiple smaller Services
- Sometimes loads!!
"Microservices"
Service Discovery is massively important
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
DNS Service Discovery in Docker
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
Every container gets a small DNS resolver
- Listen on 127.00.11.53
- Forwards requests to DNS server on Docker host
Network-scoped
Network-scoped Discovery
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
Every container gets a small DNS resolver
- Listen on 127.00.11.53
- Forwards requests to DNS server on Docker host
Network-scoped
Network-scoped Discovery
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
Every container gets a small DNS resolver
- Listen on 127.00.11.53
- Forwards requests to DNS server on Docker host
Network-scoped
vip-best load balancing
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
Every container gets a small DNS resolver
- Listen on 127.00.11.53
- Forwards requests to DNS server on Docker host
Network-scoped
vip-besed load balancing
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
Every container gets a small DNS resolver
- Listen on 127.00.11.53
- Forwards requests to DNS server on Docker host
Network-scoped
vip-besed load balancing
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
Every container gets a small DNS resolver
- Listen on 127.00.11.53
- Forwards requests to DNS server on Docker host
Network-scoped
vip-besed load balancing
Service Discovery is automatic in Docker
- For services
- For containers created with -- name or -- alias
Every container gets a small DNS resolver
- Listen on 127.00.11.53
- Forwards requests to DNS server on Docker host
Network-scoped
coming up...
Transport Layer(L4)Routing Mesh
Routing and load balance incoming connection with the Routing Mesh
(Transport Layer/Layer4)
service
service:web
Create a Swarm
$ docker swarm init...
Creates a swarm-wide overlay called ingress
Creates a service
$ docker service create...
Publish it on a port(swarm-wide)
incoming requests:
- Can hit any node
- Will resolve to the service VIP
- VIP-based load balancing will balance across all tasks in service
http Routing mesh(hrm)
Routing and load balance incoming connections with the Builds on top of port-based/L4 Routing mesh
- Allows multiple services on the same port
- Operates at the application layer(L7)
Very new at the time of recording(Application Layer/L7)
Requires Docker Datacenter*
Enable HRM - Port 80
Enable HRM- Port 80
Congrats!
Summary
questions?
