Book Image

The DevOps 2.1 Toolkit: Docker Swarm

By : Viktor Farcic
Book Image

The DevOps 2.1 Toolkit: Docker Swarm

By: Viktor Farcic

Overview of this book

Viktor Farcic's latest book, The DevOps 2.1 Toolkit: Docker Swarm, takes you deeper into one of the major subjects of his international best seller, The DevOps 2.0 Toolkit, and shows you how to successfully integrate Docker Swarm into your DevOps toolset. Viktor shares with you his expert knowledge in all aspects of building, testing, deploying, and monitoring services inside Docker Swarm clusters. You'll go through all the tools required for running a cluster. You'll travel through the whole process with clusters running locally on a laptop. Once you're confident with that outcome, Viktor shows you how to translate your experience to different hosting providers like AWS, Azure, and DigitalOcean. Viktor has updated his DevOps 2.0 framework in this book to use the latest and greatest features and techniques introduced in Docker. We'll go through many practices and even more tools. While there will be a lot of theory, this is a hands-on book. You won't be able to complete it by reading it on the metro on your way to work. You'll have to read this book while in front of the computer and get your hands dirty.
Table of Contents (22 chapters)
Title Page
Credits
About the Author
www.PacktPub.com
Customer Feedback
Preface
11
Embracing Destruction: Pets versus Cattle

Setting up a Swarm cluster


We'll continue using Docker Machine since it provides a very convenient way to simulate a cluster on a laptop. Three servers should be enough to demonstrate some of the key features of a Swarm cluster:

Note

All the commands from this chapter are available in the 02-docker-swarm.sh (https://gist.github.com/vfarcic/750fc4117bad9d8619004081af171896) Gist

for i in123; do
    docker-machine create -d virtualbox node-$i
done

At this moment, we have three nodes. Please note that those servers are not running anything but Docker Engine.

We can see the status of the nodes by executing the following ls command:

docker-machine ls

 

The output is as follows (ERROR column removed for brievity):

NAME   ACTIVE DRIVER  STATE   URL                        SWARM DOCKER
node-1 -  virtualbox  Running tcp://192.168.99.100:2376 v1.12.1
node-2 -  virtualbox  Running tcp://192.168.99.101:2376 v1.12.1
node-3 -  virtualbox  Running tcp://192.168.99.102:2376 v1.12.1

Figure 2-5: Machines running Docker...