This document discusses Docker networking and running multi-host applications. It covers networking commands, legacy networking versus new Docker networking, network aliases, single and multi-host demonstrations using Docker Swarm, the need for key-value stores, load balancing solutions, and conclusions that Docker networking is simple to set up but can become complex to understand and debug in more advanced configurations.

1. Docker Networking
Running multi-host applications
Johannes M. Scheuermann
Karlsruhe, 28.04.2016

2. Johannes M. Scheuermann
IT Engineering & Operations @ inovex
〉 Software-Defined Datacenters
〉 Infrastructure as Code
〉 Cloud technologies
〉 High Availability & Scalability
〉 @johscheuer
〉 https://github.com/johscheuer/Brownbags/tree/ma
ster/docker_networking
2

3. Some questions to you
3

4. Networking

5. Networking commands
5
ls
create
disconnect
connect
inspect
rm

6. Legacy world

7. The new (shiny)world

8. Network alias

9. Demo – single host
9
Redis-
master
Redis-
slave
Todo-app
Redis network Front network

10. Docker Swarm
10

11. 〉 Needs a K/V store
〉 etcd / consul / zookeeper
〉 Default is libnetworkfrom Docker
〉 Similiarto flannel (CoreOS)
〉 Plugins available(Calico, Weave, Flannel, ...)
Multihost networking
11

12. Compose and Networking
12

13. The missing part - Load balancing

14. Selfmade solution
14

15. Demo time
15

16. Conclusions

17. • Simpleto setup
• Many things needed to be builtaround
• Understanding everything makes it more complex
• Get’s morecomplex to debug
• Someother solutionshas built-in support
• Good choice to start with
Conclusions
17

18. My thoughts
18

19. 19
We are hiring!
www.inovexperts.com

20. Q&A

21. Johannes M. Scheuermann
inovex GmbH
Johannes.scheuermann@inovex.de
CC BY-NC-ND inovex.de +JohannesScheuermann
github.com/johscheu
er
@johscheuer youtube.com/inovexGmb
H

22. 〉 https://flic.kr/p/r7jBEn
〉 https://flic.kr/p/kRaMsy
〉 https://flic.kr/p/73VKxU
〉 https://flic.kr/p/aEHMU
Images
22