Book Image

Docker Orchestration

By : Randall Smith
Book Image

Docker Orchestration

By: Randall Smith

Overview of this book

Docker orchestration is what you need when transitioning from deploying containers individually on a single host to deploying complex multi-container apps on many machines. This book covers the new orchestration features of Docker 1.12 and helps you efficiently build, test, and deploy your application using Docker. You will be shown how to build multi-container applications using Docker Compose. You will also be introduced to the building blocks for multi-host Docker clusters such as registry, overlay networks, and shared storage using practical examples. This book gives an overview of core tools such as Docker Machine, Swarm, and Compose which will enhance your orchestration skills. You’ll learn how to set up a swarm using the decentralized building block. Next, you’ll be shown how to make the most out of the in-built orchestration feature of Docker engine and you’ll use third-party tools such as Kubernetes, Mesosphere, and CoreOS to orchestrate your existing process. Finally, you will learn to deploy cluster hosts on cloud services and automate your infrastructure.
Table of Contents (17 chapters)
Docker Orchestration
About the Author
About the Reviewer
Customer Feedback


Networking in Kubernetes is different from straight Docker, in that, IP addresses are assigned per pod rather than per container. This allows containers within a pod to connect to each other on localhost. It also allows them to act as one service. This is more akin to the traditional server model than most Docker tools. In addition, Kubernetes provides tools for doing automatic load balancing for applications and can work with most cloud providers to use their existing load balancers to provide external access.

Kubernetes requires the use of an overlay network to allow pods to communicate across the cluster. It supports GCE, Weave, Flannel, OpenVSwitch, and others either out-of-the-box or with an add-on. DNS-SD is also available out-of-the-box through the kube-dns add-on, but other services can be used instead.


Kubernetes assigns each pod an IP address, but that address will change every time the pod is restarted. In addition, the IP assigned to the pod is a private address...