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.

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 …