Skip to main content

Creating a Docker Swarm Cluster

Today we're going to be spinning up Docker Swarm! Docker Swarm is an orchestration platform (like Kubernetes) that allows you to manage a containerized environment. In 2019, I believe that Kubernetes is far more popular in the world of DevOps, but I still want to see what Docker Swarm is all about.. so let's get started!

1. Three Linux machines (I'm using Ubuntu 18.04.1 LTS servers)
2. Docker 1.12 or newer installed on all machines. At the  time of writing this, I have version 10.06.1-ce (ce stands for community edition)
3. SSH access to said machines
4. The following ports open; TCP port 2377, TCP/UDP port 7946, and UDP port 4789
5. Some type of naming convention - Because we're going to have a manager machine, pick a naming convention that is easy to remember. For example, I named my VM's dockerswarm01, dockerswarm02, and dockerswarm03. dockerswarm01 will be the management machine

For step 1, let's go ahead and SSH into each of the Linux machines. I used MobaXTerm for this so I can SSH into all from the same window. You can also use PowerShell or a Linix/OS X Terminal for this as well.

Now, ensure you're running as root by running sudo su - and typing in your password.

Next, let's initiate the Swarm cluster by running docker swarm init --advertise-addr <ip of your swarm manager>

Once you do that, your screen should look something similar to the below screenshot (yours will show a token and your current nodes GUID).

On your two other Linux machines, you're going to run the full command under the "To add a worker to this swarm, run the following command:". Ensure you run the command with the full token.

If the connection is successful, you should see a screen like the screenshot below. If you do not see this, please confirm the following;
1. Docker is running on the machine
2. You have network connectivity to the Swarm Manager
3. All of the ports were open from the pre-req section

If you run docker info on the manager, you should see some output about containers running, if swarm is active, etc.

Finally, go ahead and run docker node ls to see all of your nodes in your Docker Swarm cluster.

That's it! You've spun up your Docker Swarm cluster. Thanks for reading.


Popular posts from this blog

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …

Running PowerShell commands in a Dockerfile

As Docker continues to grow we are starting to see the containerization engine more and more on Windows. With the need for containers on Windows, we also need the same automation we get in Linux with Dockerfiles. Today we're going to create a Dockerfile that runs PowerShell cmdlets.
Prerequisites; 1. Docker for Windows
2. A code editor (VSCode preferred)

Let's go ahead and get our Dockerfile set up. Below is the Dockerfile I used for this post.

from MAINTAINER Michael Levan RUN powershell -Command Install-WindowsFeature -Name Web-Server RUN powershell -Command New-Item -Type File -Path C:\ -Name config
As you can see from the above, this is a tiny Dockerfile. What this will do is install the IIS Windows 

Feature and create a new file in C:\ called "config".
You should see something very similar to the below screenshot;

Next let's create a running container out of our image. First we'll need to run docker container ls to

 get o…

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…