Skip to main content

Docker on Windows - Part 2 Creating A Container

Welcome back and thank you for joining me on this epic journey! On part 1 of the Docker series, we went over installation and configuration of Docker on Windows. Today, we will bring down an image, create a container, give the container it's needed ports, allow it to run in the background, and see our Nginx splash page come up!

First, let's bring up our PowerShell window and do a quick docker --version to confirm Docker is installed, running, and happy. If Docker is not running, please check on Part 1 of the Docker on Windows series to confirm you followed all of the steps. Make sure to also confirm the Docker service is running.


For the purposes of this post, we're going to utilize Nginx because it's the most straight forward for learning deployments with Docker, in my opinion. It utilizes a port that's mostly open for all and the image is pre-build in the Docker hub.

Speaking of Docker hub, let's head over and take a look at the Nginx image.
https://hub.docker.com/

Go ahead and search for "Nginx" in the search bar. You'll see several images pop up. Take a look at how the first one is different. It says "official" in the name. This means that this is an official Docker image made by Nginx. The images that don't say "official" means someone else (like you or I) made the image and uploaded it to Docker hub. Let's ensure we use the official.


Next, we're going to take a look at the docker run command which we will be using to spin up our container. For more information on the docker run command, please follow this link. For today, I will explain the switches that we need for the purposes of this blog post.
https://docs.docker.com/engine/reference/commandline/run/

Our docker line is going to look like the following:

docker run --name my-nginx -tid -p 8080:80 nginx:latest

Let's break this line down:

docker = calling the Docker API
run = the command you're going to use to create the container. There are several other commands to do things like list containers, list images, etc.
--name = naming your container
tid =  t = pseudo-tty. In short, psuedo means you're interacting with an arbitrary computer and TTY means you're interacting with a console; i = interactive. Keep the STDIN open even if not inside the container for a stream of input data if needed; d = run container in background while you aren't connected to the container
p = what port you want your container to interact on. If you see something like "8080:80", this means any traffic coming into 8080, push it to 80 (http)

Let's open up a PowerShell prompt and run it!


Notice in the screenshot below how it's downloading the Nginx image. This will occur if the image you are calling hasn't been downloaded yet. If it has, it'll be sitting in your local images and this won't occur.


Next, you should see something similar to the screenshot below.


Now, let's go ahead and run docker container ls and what you should see is a running container.


Now, let's open up a web browser and go to 127.0.0.1:8080

You should see something similar to the Nginx splash page below.


Congrats! You have officially spun up your first container on Docker for Windows! The next and final blog post on our 3 part series, we will do the same thing, but in an automated fashion with Docker Compose. Stay tuned and thanks for reading!

Comments

Popular posts from this blog

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…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

Pre-reqs;
1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

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 …