Cool, but what can you ACTUALLY use containers for?

We’re going to take a bit of a sidestep this week.

I was planning on converting a Docker-Compose project into a Kubernetes one, but I had a small project pop up this week. That project involved me setting up a container to mimic a production environment so I could test my script without disrupting any of our clients.

Figured a practical example of how a container saved the day would be a better topic than me learning something just to learn something.

Every once in awhile I’m given a task that, once explained to me, seems like it’s going to take a lot of time. Like hours of my attention every time this bit of work comes up.

I’ll usually ask how often this task comes up in a given quarter. If the combined time for a quarter is more than a day or two, I usually throw the XKCD comic on automation out the window just go for it.

Continue reading Cool, but what can you ACTUALLY use containers for?

Day 4: Scripting Docker Commands With

In Day 3, I included a blurb from my DevOps-y friends about the natural progression of abstractions on top of containers:

You usually start with docker run CLI commands and graduate to tools with more layers of abstraction as you need them. Docker-compose comes next, followed by automating several commands with Bash scripts, which is eventually followed by Kubernetes.

I also shared with you a better way to handle switches in Bash scripts. Today I’ll show you how I moved from running my own Docker commands to running off of one shell script with a handful of flags.

Continue reading Day 4: Scripting Docker Commands With

Day 3: Fun With Flags

First off, some housekeeping. I can already tell that coming up with a daily post is going to be harder than my buddy Alex had with his SVG work. He had one animation to complete every day. I’m spending all month working towards one larger goal.

However, I’ll do my best to share something I learn every day, even if it’s small.


I bought Nigel Poulton’s book bundle from LeanPub and am starting to dig into those, but learned something neat recently that I thought I would share.

When I was still at the courts, I was teaching myself how to use containers as quickly as I was implementing them in projects. While learning how to manage multiple sets of containers, I spoke with my college friends who were in DevOps-y roles about the tools they used. It shocked me to hear everyone say the same thing:
Continue reading Day 3: Fun With Flags

Day 2: What’s the plan?

In the spirit of learning in public, I wanted to share why I picked Kubernetes as the topic of my deep dive, what my defined goals are for the end of the month, and what my learning plan looks like in order to get me over the finish line.
As short as a month can feel, this is a marathon; not a sprint. Let’s take these in order:
1. Why did I pick K8s?
I have a bit of a weird background: computer nerd in a high school with no computer courses -> Champlain College CNIS student -> DBA at the US Courts -> web developer at the US Courts -> web and infrastructure developer for the AO of the US Courts -> DevOps Engineer at Clarity Software Solutions.

Continue reading Day 2: What’s the plan?

Day 1: Learning DevOps In Public

Hi, my name is Henry Quinn and in July I’ll be “learning in public.”

Last month, my buddy Alex Trost started a learn in public month after reading this post by Shawn Wang. In 30 short days he really upped his game with SVG animations (enough where he was asked to create an eLearning course about it), so I figure there must actually be some benefit to learning, and then teaching, something new every day.

Continue reading Day 1: Learning DevOps In Public