Skip to main content

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('https://chocolatey.org/install.ps1'))

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 a similar output as below:

PS C:\WINDOWS\system32> choco 
Chocolatey v0.10.11 
Please run 'choco -?' or 'choco -?' for help menu.

Next, we're going to install the Docker CLI so we can utilize the API. Run the following:

choco install docker

 You should see something like the below screenshot.



Confirm Docker installed successfully by simply running docker --version  and you'll see your version number. Please note: Your version may be different than mine.



Now that we have the Docker CLI installed, we need to download Docker for Windows. Please visit https://docs.docker.com/docker-for-windows/install/ and sign up for a free account. Once you do that, you'll be able to continue.


Click on the "Get Docker" button as shown above and it'll start the .EXE. Once completed, go ahead and open that up. You should see a similar window as below.



For the purposes of this blog, feel free to not check "Use Windows containers instead of Linux containers (this can be changed after installation".

Once complete, go ahead and search for Docker, then open. It'll take a short while to get the services up and running.

Go ahead and run get-service *docker* in a PowerShell window to confirm the service is running successfully. 



To confirm that Docker is successfully running, open up a PowerShell prompt and run docker run hello-world and you should see something very similar to the below screenshot:


That's it for this tutorial! Feel free to of course play around and test (in fact, I encourage it). Up next is running a container with Docker on Windows and Docker Compose!

Comments

Popular posts from this blog

So, you want to be a Cloud Engineer?

In 2019 one of the biggest pieces of tech is the cloud. Whether it be public cloud or private cloud, cloud technologies are here to stay (for now). I predict that Cloud Engineering will be a very big part of IT (and development) for another 5-10 years. Today I want to share with you my journey in becoming a Cloud Engineer and some helpful tips. A career timeline to be a Cloud Engineer can go like so;

Desktop Support > Junior Sysadmin > Sysadmin > Sysadmin/Technical Lead > Engineer >  Cloud Engineer.

Although our career paths may not align, I believe that this progression is very import. Let me tell you why.



Helpdesk/Desktop Support Helpdesk and desktop support get your feet wet. It allows you to understand technology and how it's used in the workplace from a business perspective. It shows you what technologies may be best in the current environment your in and how to support those technologies. It also teaches you soft skills and how to support people from a technic…

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…

Spinning up a Kubernetes cluster with Kubeadm

In today's world, we have several public cloud technologies that will ultimately help us with spinning up these infrastructures. This however comes with a price. Because a public cloud provider (like AWS or Azure) handles the API/master server and networking, you'll get something up quick, but miss some key lessons of spinning up a Kubernetes cluster. Today, I'll help you with that.

There are some pre-reqs for this blog:
1. At least 3 VM's. In my case, I'm using my ESXi 6.7 server at home.
2. Basic knowledge/understanding of what Kubernetes is utilized for.
3. Windows, Mac, or Linux desktop. For this blog, I am using Windows 10.

The first thing you want to do is spin up three virtual machines running Ubuntu18.04. You can use a RHEL based system, but the commands I show and run (including the repos I'm using) will be different.

I have already set up my 3 virtual machines. I gave them static IP addresses as I have found API/configuration issues if the VM shuts do…