{"id":39157,"date":"2016-10-13T15:56:09","date_gmt":"2016-10-13T10:26:09","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=39157"},"modified":"2016-11-02T11:35:20","modified_gmt":"2016-11-02T06:05:20","slug":"docker-swarm-multi-manager-setup","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/docker-swarm-multi-manager-setup\/","title":{"rendered":"Docker Swarm Multi-Manager Setup"},"content":{"rendered":"

Docker Swarm has gained a lot of popularity in the last few months. It is Docker’s orchestration tool. Docker has been coming up with a lot of updates and Docker Swarm is very stable as compared to when it was launched. It is as Docker says “Production Ready.” You can go through the\u00a0blog written by my colleague on\u00a0how to setup Docker Swarm on AWS <\/a>.<\/p>\n

\"Screenshot<\/p>\n

In this blog, I will be using Docker Machine<\/strong> to create my Docker Swarm nodes and masters using virtual box driver. Also, I will be using another virtual machine to set up Consul for Nodes and Masters discovery. Then I will also show you how setup HA for Docker Swarm Master (manager). So, let’s get started.<\/p>\n

Consul will be used for node discovery. For now, I just have multiple Consul containers in one virtual box Docker Machine. For production, we can put those on different machines for HA.<\/p>\n

Prerequisites<\/h1>\n

1. Docker Machine should installed. Install it from here<\/a>.
\n2. VirtualBox installed should be above version 4.0.
\n3. Docker Engine should be present on your local machine.<\/p>\n

Steps To Setup Your Swarm<\/h1>\n

1. First, we will create a machine for Consul. \u00a0Use the following command to create Consul machine:<\/p>\n

[js]docker-machine ls
\n(to check the current state and details of machines)<\/p>\n

docker-machine create -d=virtualbox consul-machine
\n(-d means driver for docker-machine, you can even use –driver virtualbox [\/js]<\/p>\n

Other drivers like AWS<\/a> are also supported which will bring up new EC2 instances and make them a Docker Machine. You can read more on Docker documentation website.<\/p>\n

Just connect to the machine using:<\/p>\n

[js]docker-machine ssh\u00a0machine-name [\/js]<\/p>\n

Now, you just need to create a Docker Compose file and enter the following contents:<\/p>\n

[js]
\nmyconsul:
\n image: progrium\/consul
\n restart: always
\n hostname: consul
\n ports:
\n – 8500:8500
\n command: "-server -bootstrap"
\n[\/js]<\/p>\n

Install docker-compose from in the Consul machine by following the steps mentioned\u00a0here<\/a>.
\nNow, run the below command inside the Consul\u00a0machine to get Consul up and running:<\/p>\n

[js]docker-compose up -d
\n(if the filename of the compose file is docker-compose.yml else pass the filename explicitly using -f switch) [\/js]<\/p>\n

Just do a docker ps<\/strong> and netstat\u00a0<\/strong>–ntlp<\/strong> to check Consul is running on 8500 port of this machine.<\/p>\n

2. Now that Consul is setup, let’s set up the two managers (masters) for Docker Swarm, one being primary and the other being a standby. This can be done simply by using the following two commands:<\/p>\n

[js]
\ndocker-machine create -d virtualbox –swarm \\
\n –swarm-master \\
\n –swarm-opt replication \\
\n –swarm-discovery consul:\/\/192.168.99.114:8500 \\
\n –engine-opt cluster-store=consul:\/\/192.168.99.114:8500 \\
\n manager-0
\n[\/js]<\/p>\n

The command above will bring your first manager up, and the command given below should bring the next one up:<\/p>\n

[js]
\ndocker-machine create -d virtualbox –swarm \\
\n –swarm-master \\
\n –swarm-opt replication \\
\n –swarm-discovery consul:\/\/192.168.99.114:8500 \\
\n –engine-opt cluster-store=consul:\/\/192.168.99.114:8500 \\
\n manager-1
\n[\/js]<\/p>\n

To connect to any of these managers, use the below given command:<\/p>\n

[js]eval $(docker-machine env\u00a0manager-0)[\/js]<\/p>\n

We will connect to the Swarm after the nodes are up. So, let’s move on to that.<\/p>\n

3. Bringing up the nodes is just similar to using the above command without the –swarm-master<\/strong>. Use the command:<\/p>\n

[js]docker-machine create -d virtualbox –swarm –swarm-discovery consul:\/\/192.168.99.114:8500 –engine-opt cluster-store=consul:\/\/192.168.99.114:8500 node-1 [\/js]<\/p>\n

4. Let’s connect to the Docker Swarm manager’s engine. For doing that just run the following command:<\/p>\n

[js]eval $(docker-machine env\u00a0–swarm manager-0)[\/js]<\/p>\n

Run docker ps<\/strong> to see what containers are running in the swarm, and it should show none.<\/p>\n

Now, let’s run a new container say Ubuntu in the Swarm. By default new containers in the Swarm run on the nodes, manager-0. If you wish that containers never come up on the manager then just use drain on the manager. Now, run a container using the command:<\/p>\n

[js]docker run -itd\u00a0–name ubuntu1 ubuntu[\/js]<\/p>\n

Do a docker ps<\/strong> and see. It will show, on which node the container is running:<\/p>\n

\"Screenshot<\/p>\n

So, now you’re connected to Docker Swarm and every new container comes up in the Swarm.<\/p>\n

To work inside any of these containers, you can login to the nodes or else from the manager you can just run docker exec -it container-name bash<\/strong> (bash or any other command) to get into the desired container.
\nThere are some other features like you can launch a container on a node with a specific name, or where similar types of container are running using label<\/strong> and affinity<\/strong>.<\/p>\n

5. Let’ see what happens if our primary manager goes down:<\/p>\n

\"Screenshot<\/p>\n

Running command to stop the manager-0:<\/p>\n

\"Screenshot<\/p>\n

Now, checking info of manager-1:<\/p>\n

\"Screenshot<\/p>\n

Woohoo! The secondary manager is now the primary. So, this is how you can easily setup your own Docker Swarm. The blog also portrays how failover of managers takes place in Docker Swarm using Docker<\/a> Machine.<\/p>\n","protected":false},"excerpt":{"rendered":"

Docker Swarm has gained a lot of popularity in the last few months. It is Docker’s orchestration tool. Docker has been coming up with a lot of updates and Docker Swarm is very stable as compared to when it was launched. It is as Docker says “Production Ready.” You can go through the\u00a0blog written by […]<\/p>\n","protected":false},"author":174,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":25},"categories":[1174,2348,1],"tags":[2366,3866,1892,1883,2651,4121,2590,4120,4119,4122],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/39157"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/174"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=39157"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/39157\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=39157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=39157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=39157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}