Book Image

Windows Subsystem for Linux 2 (WSL 2) Tips, Tricks, and Techniques

By : Stuart Leeks
Book Image

Windows Subsystem for Linux 2 (WSL 2) Tips, Tricks, and Techniques

By: Stuart Leeks

Overview of this book

Windows Subsystem for Linux (WSL) allows you to run native Linux tools alongside traditional Windows applications. Whether you’re developing applications across multiple operating systems or looking to add more tools to your Windows environment, WSL offers endless possibilities. You’ll start by understanding what WSL is and learn how to install and configure WSL along with different Linux distros. Next, you'll learn techniques that allow you to work across both Windows and Linux environments. You’ll discover how to install and customize the new Windows Terminal. We'll also show you how to work with code in WSL using Visual Studio Code (VS Code). In addition to this, you’ll explore how to work with containers with Docker and Kubernetes, and how to containerize a development environment using VS Code. While Microsoft has announced support for GPU and GUI applications in an upcoming release of WSL, at the time of writing these features are either not available or only in early preview releases. This book focuses on the stable, released features of WSL and giving you a solid understanding of the amazing techniques that you can use with WSL today. By the end of this book, you’ll be able to configure WSL and Windows Terminal to suit your preferences, and productively use Visual Studio Code for developing applications with WSL.
Table of Contents (16 chapters)
1
Section 1: Introduction, Installation, and Configuration
5
Section 2:Windows and Linux – A Winning Combination
11
Section 3: Developing with the Windows Subsystem for Linux

Summary

In this chapter, you've been introduced to containers and have seen how they enable an application and its dependencies to be packaged together to enable it to be run simply on a machine with the Docker daemon running. We discussed Docker registries as a way of sharing images, including the commonly used public registry: Docker Hub. You were introduced to the docker CLI and used this to run the nginx image from Docker Hub, with Docker automatically pulling the image to the local machine from Docker Hub.

After running the nginx image, you saw how to build an image from a custom web application using steps defined in a Dockerfile. You saw how Docker builds image layers for steps in the Dockerfile and reuses them in subsequent builds if files haven't changed, and also how this can be used to improve subsequent build times by carefully structuring the Dockerfile so that the most commonly changing content is added in later steps.

After looking at how to work with...