Downloaded 155 times
![7
docker network create
mrjana@dev-1:~$ docker network create --help
Usage: docker network create [OPTIONS] NETWORK-NAME
Creates a new network with a name specified by the user
--aux-address=map[] auxiliary ipv4 or ipv6 addresses used by
Network driver
-d, --driver=bridge Driver to manage the Network
--gateway=[] ipv4 or ipv6 Gateway for the master subnet
--help=false Print usage
--ip-range=[] allocate container ip from a sub-range
--ipam-driver=default IP Address Management Driver
-o, --opt=map[] set driver specific options
--subnet=[] subnet in CIDR format that represents a network
segment](https://image.slidesharecdn.com/networkingdeepdive1-160316194103/85/DockerCon-EU-2015-Docker-Networking-Deep-Dive-7-320.jpg)
![7
docker network create
mrjana@dev-1:~$ docker network create --help
Usage: docker network create [OPTIONS] NETWORK-NAME
Creates a new network with a name specified by the user
--aux-address=map[] auxiliary ipv4 or ipv6 addresses used by
Network driver
-d, --driver=bridge Driver to manage the Network
--gateway=[] ipv4 or ipv6 Gateway for the master subnet
--help=false Print usage
--ip-range=[] allocate container ip from a sub-range
--ipam-driver=default IP Address Management Driver
-o, --opt=map[] set driver specific options
--subnet=[] subnet in CIDR format that represents a network
segment](https://image.slidesharecdn.com/networkingdeepdive1-160316194103/75/DockerCon-EU-2015-Docker-Networking-Deep-Dive-7-2048.jpg)
Uploaded byDocker, Inc.
DockerCon EU 2015: Docker Networking Deep Dive
The document discusses advancements in Docker networking highlighted in version 1.9, covering features such as multiple network types, service discovery, and security enhancements. It details new capabilities like micro-segmentation, cloud portability, and a user-friendly API for creating networks. Additionally, it showcases practical use cases for deploying applications using Docker's networking features.
More Related Content
Similar to DockerCon EU 2015: Docker Networking Deep Dive
DockerCon EU 2015: Docker Networking Deep Dive
- 1. Docker Networking Deep Dive DaveTucker Product Manager Jana Radhakrishnan Senior Software Engineer
- 2. Agenda What's Next? IPv6 Service Discovery Security Bettertogether Deploying an app using Swarm, Compose and Networking What's in 1.9 Overview Bridge Driver Overlay Driver Default Gateway service Use Cases Microsegmentation Multi-Tenancy Cloud portability
- 3. What's in 1.9? Lot'sof networking awesomeness
- 4. — Moby Dock “Transformnetworking, like Docker did for compute” 4
- 5. 5 • New top-levelUX & API: docker network • Multiple micro-segmented networks • Connect containers to multiple networks • Multi-host networking • Pluggable • Network driver plugins • IP Address Management plugins Features available in 1.9
- 6. 6 • A Network... •Interconnects a set of containers • Provides isolation for these containers • Every network is backed by a driver • Networks are scoped as Local or Global • Scope is chosen based on negotiated driver scope Networks and Scopes
- 7. 7 docker network create mrjana@dev-1:~$docker network create --help Usage: docker network create [OPTIONS] NETWORK-NAME Creates a new network with a name specified by the user --aux-address=map[] auxiliary ipv4 or ipv6 addresses used by Network driver -d, --driver=bridge Driver to manage the Network --gateway=[] ipv4 or ipv6 Gateway for the master subnet --help=false Print usage --ip-range=[] allocate container ip from a sub-range --ipam-driver=default IP Address Management Driver -o, --opt=map[] set driver specific options --subnet=[] subnet in CIDR format that represents a network segment
- 8. Bridge Network Driver 8 C1 Docker0br-ee40a8236479 Host NIC X Docker Host C2 C3 C4 C5 C6
- 9. Multi-host Networking KV Store DockerHost Docker Host Docker Host C1 C2 C3 C4 C5 C6 C7 C8 C9
- 10. Overlay Network Driver 10 C1 C2 C3 C5 C4 br0 Veth Veth Veth HostNIC VXLAN Host NIC br0 Veth Veth VXLAN Docker Host 1 Docker Host 2
- 11. Overlay Control Plane 11 KVSTORE Serf IP Address allocation VXLAN ID allocation (Network, subnet) -> VXLAN ID Populate Neighbor Table entries Populate L2 FDB entries Populate Neighbor Table entries Populate L2 FDB entries Docker Host 1 Docker Host 2
- 12. Default gateway service 12 C2 Overlay Network2 default_gw bridge C1 Overlay Network 1 ICC=false Port Mapping & NAT Happens here
- 13. Use Cases How touse Docker's new networking
- 14.
- 15.
- 16. Use Case: CloudPortability 16 Network "ubercloud" aws do
- 17. What's Next? More awesome,coming soon
- 18. Better IPv6 Support -IPv6 that just works out of the box - IPv6 address allocation - Static public address assignments - Bridge Network and Overlay Network - Support for AAAA record resolution
- 19. Service Discovery - DNSbased service discovery - Register one or more containers as providing a "service" within a network - Provide DNS records to allow the service to be discovered
- 20. Security - Encryption forthe Overlay Network - Official "proxy" container for tying networks together - Like in the micro-segmentation use case - "Offline" networks
- 21. Better together Deploying anapplication with networking
- 22. — Dave Tucker “TakingKitematic's Minecraft Demo and turning it up to eleven ” 22
- 23. The problem statement -Deploy a Minecraft server - Support multiple worlds, one for each mode of play - Central lobby - Survival world - Creative world
- 24.
- 25.
- 26. See it inaction!
- 27. Thank you! Dave Tucker @dave_tucker dt@docker.com JanaRadhakrishnan @mrjana jana@docker.com
- 28.
- 29.
- 30. Day in thelife of packet 30 C1 ARP Request br0 Flood ARP Request Src VXLAN Interface Proxy ARP Response C1 br0 Full IP packet with L2 header Flood IP packet Src VXLAN InterfaceLookup FDB Send VXLAN packet Src Host NICSend on the wire Dst Host NICProcess VXLAN Encap Dst VXLAN Interface Send original IP packet over bridge br0 Flood IP packet C2
- 31. Classic three tierapplication App WebDB Front End Network Back End Network