Skip to main content


Showing posts from November, 2018

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.

Docker on Windows - Part 1 Installation & Configuration

As we go through the journey of distributed applications and containers, there's an up-and-comer, Microsoft. Microsoft has been in the container game since Server 2016, and it is now available on Windows 10.

In this blog post, we're going to go over the configuration with PowerShell, Chocolatey, and Docker. First things first, lets confirm you have chocolatey installed. Chocolatey is a package manager, like brew, yum, or aptitude. To install Chocolatey, open up a PowerShell prompt as an administrator and run the following:

Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString(''))

This does the following:
1. Sets an execution policy to bypass for this installation
2. Forces the installations, which means no prompts
3. Utilizes a .NET object System.Net.WebClient to make an API call to Chocolatey.

Now that this is installation, let's confirm by running 'choco'. You should see…

Python3 and AWS

So, here we are. Deep into cloud architecture, getting our feet wet in application deployment/distributed systems, and we find ourselves doing a ton of manual tasks. These manual tasks could be point/click, or they could be simply re-running the same aws cli commands over and over again. We're going to use another way to hit the AWS API, and that's with Python.

PLEASE NOTE: The code is pasted at the bottom. Feel free to copy/paste it while we're going over it. I have screenshots for a visual as well.

Python has an amazing module (one of it's best in my opinion) called Boto3. Boto3 is a library/module to AWS's API. Similar to AWS CLI, all you need is a secret key/access key.

For this blog, we're going to list EC2 instances.
You will need the following to follow along:
PyCharm for the IDEAn internet connectionAn AWS account that has access to EC2 (please don't experiment in your prod environment).A coffee, or a beerPrior knowledge of functions, if statements, …