Demystifying Docker Networking Devoxx MA 2017
•
0 likes•145 views
Devoxx Morocco 2017 Title : Demystifying Docker Networking Track : Cloud-computing, Containers and Virtualisation. More details : https://cfp2017.devoxx.ma/2017/speaker/imad_hsissou
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Demystifying Docker Networking Devoxx MA 2017
Similar to Demystifying Docker Networking Devoxx MA 2017 (20)
Recently uploaded
Recently uploaded (20)
Demystifying Docker Networking Devoxx MA 2017
- 3. TL;DR #DockerNet @hsissouimad • Docker What ? • Single-host Networking • Multi-host Networking • Docker as used by Network Engineers • Pipework
- 5. Docker What ? #DockerNet @hsissouimad • Open Source engine to commoditize Linux Containers (known as LXC) • LXC (LinuX Containers) let you run a Linux system within another Linux system • A container is a group of processes on a Linux box, put together in an isolated environment • Inside the box, it looks like a VM. Outside the box, it looks like normal processes.
- 14. Living inside a single host #DockerNet @hsissouimad eth0 10.0.10.4/16 LAN
- 15. Let’s start with a regular host #DockerNet @hsissouimad
- 16. Say hi to docker0 #DockerNet @hsissouimad
- 17. docker run –it alpine sh #DockerNet @hsissouimad
- 18. docker run –it alpine sh (again) #DockerNet @hsissouimad
- 19. Container perspective #DockerNet @hsissouimad root@devoxx-ma:~# docker run -it alpine sh / # ip a <Snip> 5: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff inet 172.17.0.2/16 scope global eth0 valid_lft forever preferred_lft forever <Snip> CTRL + PQ to detach
- 20. Host perspective #DockerNet @hsissouimad root@devoxx-ma:~# docker network inspect bridge <Snip> "Containers": { "9b14d7480d78611d1817abeb0 ..": { "Name": "dreamy_galileo", "EndpointID": "a1f27b05c3bef4f ..", "MacAddress": "02:42:ac:11:00:02", "IPv4Address": "172.17.0.2/16", "IPv6Address": "" } }, <Snip>
- 21. Host perspective #DockerNet @hsissouimad root@devoxx-ma:~# ifconfig docker0 | grep 'inet' inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 root@devoxx-ma:~# brctl show bridge name bridge id interfaces docker0 8000.02423e711c09 veth21a9b0a
- 22. Test network connectivity #DockerNet @hsissouimad root@devoxx-ma:~# docker attach dreamy_galileo / # ping 172.17.0.3 PING 172.17.0.3 (172.17.0.3): 56 data bytes 64 bytes from 172.17.0.3: seq=0 ttl=64 time=0.616 ms 64 bytes from 172.17.0.3: seq=1 ttl=64 time=0.128 ms 64 bytes from 172.17.0.3: seq=2 ttl=64 time=0.129 ms 64 bytes from 172.17.0.3: seq=3 ttl=64 time=0.213 ms ^C --- 172.17.0.3 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 0.128/0.271/0.616 ms / #
- 23. User-defined networks #DockerNet @hsissouimad $ docker network create devoxx-network $ docker network create -d bridge --subnet 172.72.0.0/16 devoxx-network $ docker run --network=devoxx-network -itd --ip=172.72.4.1 alpine
- 24. docker0 ip address #DockerNet @hsissouimad Default docker0 IP is not 172.17.42.1/16 (since version 1.9.0) it’s now 172.17.0.1/16
- 25. Iptables magic (Demo) #DockerNet @hsissouimad docker run -d -p 8080:80 nginx What happens when you type this ?
- 34. docker network ls (before swarm) #DockerNet @hsissouimad root@devoxx-ma-node1:~# docker network ls NETWORK ID NAME DRIVER SCOPE 48422e8a759a bridge bridge local bc11ca59e46c host host local 58058e6fe378 none null local
- 35. docker swarm init #DockerNet @hsissouimad root@devoxx-ma-node1:~# docker swarm init Swarm initialized: current node (xavrlc61fi83zdhxb51p55xmy) is now a manager. To add a worker to this swarm, run the following command: docker swarm join --token SWMTKN-1- 5mosmewivdfjtym5evqyumqulqvptqiiq6udt394ubvfiuqgr1- 5j0w7wtqe0az060mtqqcjwghc 138.68.165.47:2377
- 36. docker swarm init --advertise-addr #DockerNet @hsissouimad root@devoxx-ma-node1:~# docker swarm init -- advertise-addr 138.68.165.47:2377 Swarm initialized: current node (xavrlc61fi83zdhxb51p55xmy) is now a manager. To add a worker to this swarm, run the following command: docker swarm join --token SWMTKN-1- 5mosmewivdfjtym5evqyumqulqvptqiiq6udt394ubvfiuqgr1- 5j0w7wtqe0az060mtqqcjwghc 138.68.165.47:2377
- 37. docker swarm join --token (Node 2) #DockerNet @hsissouimad root@devoxx-ma-node2:~# docker swarm join --token SWMTKN-1-5mosmewiv5evq4u 138.68.165.47:2377 This node joined a swarm as a worker.
- 38. docker node ls #DockerNet @hsissouimad root@devoxx-ma-node1:~# docker node ls ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS xavrl * devoxx-ma-node1 Ready Active Leader c3gyt devoxx-ma-node2 Ready Active
- 39. docker network ls (after swarm) #DockerNet @hsissouimad root@devoxx-ma-node1:~# docker network ls NETWORK ID NAME DRIVER SCOPE c1d369da0672 bridge bridge local ae21837a0f3f docker_gwbridge bridge local 4fd7f5302ddf host host local b9o4m4tdhsnm ingress overlay swarm 5f80a2dd1f15 none null local
- 40. Create an overlay network #DockerNet @hsissouimad root@devoxx-ma-node1:~# docker network create -d overlay devoxx-overlay 7c2fmnrwvbcopx5vcnitpnvye
- 41. docker network ls (after overlay) #DockerNet @hsissouimad root@devoxx-ma-node1:~# docker network ls NETWORK ID NAME DRIVER SCOPE c1d369da0672 bridge bridge local 7c2fmnrwvbco devoxx-overlay overlay swarm ae21837a0f3f docker_gwbridge bridge local 4fd7f5302ddf host host local b9o4m4tdhsnm ingress overlay swarm 5f80a2dd1f15 none null local
- 42. Create a service #DockerNet @hsissouimad root@devoxx-ma-node1:~# docker service create --name sleep --network devoxx-overlay - -replicas 2 ubuntu sleep infinity 134kzekwb6wj0axj4s5ymgtmh
- 43. docker service ls #DockerNet @hsissouimad $ docker service ls
- 44. docker service ps <SERVICE> #DockerNet @hsissouimad $ docker service ps sleep
- 47. Thank you .. You’re All Awesome ! #DockerNet