Skip to main content

Windows Subsystem For Linux

So.. Windows Subsystem....for....Linux? Bash? On Windows? Why yes, let's check it out.

What is this strange cross-platform, dual-booting witchcraft? Well, the first thing I can assure you is that it's not dual-booting. The second thing I'm 90% sure of is that it's not witchcraft.

Windows Subsystem for Linux is essentially as it sounds, it's a "sub" (child) kernal running right on your Windows 10 desktop. Even better? You can find the Linux kernals right in the Windows store. First, let's install Ubuntu and Kali.

1) Open up the Windows Store and search "Windows Subsystem For Linux". You will see a pop-up to run Linux. When you click that, you will see all of the current distros.

2) Click whichever distros you want to install. In my case, I'm going to install Ubuntu and Kali.

3) Click "get" and once it's installed, you can launch. You can also click in your search bar and find your distros

4) First thing you will see when you open is a message stating "The Windows Subsystem for Linux optional component is not enabled. Please enable it and try again. We will now enable with PowerShell.

5) We are going to use a short line. Please copy and paste this into a PowerShell host and run that host as admin.

6) Once you open your Subsystem, you will see the the kernal installing.

7) You will be prompted to put in your username and a new password.

8) Once you type in your new credentials, you will see your command prompt. Please note, you do not change hostnames. It takes the hostname of your primary host. Remember, "subsystem".

Once you're in, it's time to explore! You will see that you can do the same thing you can do in Linux. For example, I can CD to var and see my directories.

As you can see, I can even CD into my C: drive. If you go to your root (/) and the "mnt" directory, you will see your other drive letters on your Windows machine.

And that's it! Now it's time for you to go play and see for yourself.


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.

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…

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…