WSL 2 Introduction for Beginners.

By /

Okay, here’s a comprehensive article on WSL 2, designed for beginners, aiming for approximately 5000 words:

WSL 2: A Deep Dive for Beginners – Unleashing the Power of Linux on Windows

Introduction: Bridging the Gap Between Windows and Linux

For years, developers and IT professionals who preferred the power and flexibility of Linux found themselves in a bit of a bind when working on Windows machines. They often had to resort to dual-booting (installing both Windows and Linux on the same computer and choosing which one to boot into), using virtual machines (running Linux inside a virtualized environment within Windows), or relying on tools like Cygwin (which provides a Linux-like environment on Windows but isn’t a full Linux kernel). These solutions, while functional, often came with performance overhead, compatibility issues, or a less-than-seamless experience.

Enter the Windows Subsystem for Linux (WSL), a revolutionary feature introduced by Microsoft that fundamentally changed the game. WSL allows you to run a genuine Linux environment – including most command-line tools, utilities, and applications – directly on Windows, without the overhead of a traditional virtual machine or the complexities of dual-booting. This means you can leverage the best of both worlds: the familiarity and widespread software support of Windows combined with the robust development tools and open-source ecosystem of Linux.

WSL has gone through two major iterations: WSL 1 and WSL 2. While WSL 1 was a significant step forward, WSL 2 represents a monumental leap, offering dramatically improved performance and compatibility. This article will focus primarily on WSL 2, explaining what it is, how it works, how to install and configure it, and how to get started using it effectively.

What is WSL 2? A New Architecture

WSL 2 isn’t just an incremental update to WSL 1; it’s a complete architectural redesign. The key difference lies in how WSL 2 interacts with the Windows kernel.

  • WSL 1 (Translation Layer): WSL 1 used a translation layer to convert Linux system calls (the way Linux applications interact with the kernel) into Windows NT kernel calls. This approach worked for many applications, but it struggled with certain system calls, particularly those related to file system operations. This resulted in slower file system performance compared to native Linux or even a virtual machine.

  • WSL 2 (Lightweight Virtual Machine): WSL 2, on the other hand, runs a real Linux kernel inside a lightweight, highly optimized virtual machine. This VM utilizes a subset of Hyper-V features, but it’s not a full-blown virtual machine in the traditional sense. It’s designed to be incredibly fast to start, consume minimal resources, and integrate seamlessly with Windows. Because it’s a real Linux kernel, WSL 2 offers full system call compatibility. This means virtually any Linux application that runs on a standard Linux distribution will run flawlessly within WSL 2.

Key Benefits of WSL 2:

  • Significantly Improved File System Performance: This is arguably the biggest advantage of WSL 2. File I/O operations, which were a bottleneck in WSL 1, are dramatically faster in WSL 2, often matching or even exceeding the performance of a traditional virtual machine. This is crucial for development tasks like compiling code, running build systems, and working with large datasets.

  • Full System Call Compatibility: As mentioned earlier, WSL 2’s use of a real Linux kernel ensures that virtually any Linux application will run without modification. This eliminates the compatibility issues that sometimes plagued WSL 1.

  • Faster Boot Times: WSL 2 instances start up in a matter of seconds, making it incredibly convenient to jump in and out of your Linux environment.

  • Dynamic Resource Allocation: WSL 2 dynamically allocates resources (CPU, memory) to the Linux VM as needed. This means it only uses the resources it requires, minimizing the impact on your Windows system’s performance.

  • Seamless Integration with Windows: WSL 2 provides excellent integration with Windows. You can:

    • Access Windows files from within Linux.
    • Access Linux files from within Windows.
    • Run Windows executables from within Linux.
    • Run Linux GUI applications (with some configuration – more on this later).
    • Use Windows tools like Visual Studio Code to develop directly within your WSL 2 environment.

  • Docker Desktop Integration: WSL 2 provides a backend for Docker Desktop on Windows, dramatically improving the performance and resource utilization of Docker containers. This is a significant advantage for developers working with containerized applications.

System Requirements for WSL 2:

Before you can install WSL 2, you need to make sure your system meets the following requirements:

  • Windows 10 or Windows 11:
    • For x64 systems: Version 1903 or higher, with Build 18362 or higher.
    • For ARM64 systems: Version 2004 or higher, with Build 19041 or higher.
  • Virtualization Enabled: You need to enable virtualization in your computer’s BIOS or UEFI settings. This setting is usually called “Virtualization Technology,” “VT-x,” “AMD-V,” or something similar. The exact name and location of the setting vary depending on your motherboard manufacturer. You’ll typically find it in the CPU or security settings.
  • Virtual Machine Platform feature enabled: This optional Windows Feature needs to be enabled.

Installation and Configuration: A Step-by-Step Guide

Now, let’s walk through the process of installing and configuring WSL 2 on your Windows machine.

Step 1: Enable the Windows Subsystem for Linux (Optional Feature)

  1. Open the Start Menu and type “Turn Windows features on or off”. Click on the result.
  2. In the “Windows Features” window, scroll down and check the box next to “Windows Subsystem for Linux”.
  3. Click “OK”. Windows will install the necessary components and may prompt you to restart your computer.

Step 2: Enable the Virtual Machine Platform (Optional Feature)

  1. Open the Start Menu and type “Turn Windows features on or off”. Click on the result.
  2. In the “Windows Features” window, scroll down and check the box next to “Virtual Machine Platform”.
  3. Click “OK”. Windows will install the necessary components and may prompt you to restart your computer.

Step 3: Set WSL 2 as the Default Version

  1. Open PowerShell as an administrator. Right-click on the Start Menu and select “Windows PowerShell (Admin)” or “Windows Terminal (Admin)”.

  2. Run the following command:

    powershell
    wsl --set-default-version 2

    This command sets WSL 2 as the default version for any new Linux distributions you install.

Step 4: Install a Linux Distribution

You can install Linux distributions from the Microsoft Store or from the command line. The Microsoft Store method is generally easier for beginners.

Method 1: Installing from the Microsoft Store

  1. Open the Microsoft Store.
  2. Search for your desired Linux distribution (e.g., “Ubuntu,” “Debian,” “Kali Linux,” “openSUSE”).
  3. Click on the distribution you want and then click “Get” (or “Install”).
  4. Once the download and installation are complete, click “Launch”.
  5. The first time you launch a distribution, it will take a few minutes to complete the installation process. You’ll be prompted to create a user account and password for your Linux environment. This user account is separate from your Windows user account.

Method 2: Installing from the Command Line

  1. Open PowerShell as an administrator.

  2. To see a list of available distributions, run:

    powershell
    wsl --list --online

  3. To install a distribution, use the following command, replacing DistributionName with the name of the distribution you want (e.g., Ubuntu-20.04):

    powershell
    wsl --install -d DistributionName
    For example to install Ubuntu 20.04:
    powershell
    wsl --install -d Ubuntu-20.04

  4. The first time you launch a distribution, it will take a few minutes to complete the installation process. You’ll be prompted to create a user account and password for your Linux environment.

Step 5: Verify Installation

  1. Open PowerShell (you don’t need to be an administrator for this step).

  2. Run the following command:

    powershell
    wsl -l -v

    This command lists all installed Linux distributions and their WSL version. You should see your installed distribution listed with a version of “2”. If it shows “1”, you can convert it to WSL 2 using the following command (replace DistributionName with the name of your distribution):

    powershell
    wsl --set-version DistributionName 2
    The conversion process might take some time, depending on the size of your distribution.

Accessing Your Linux Environment

Once you’ve installed a Linux distribution, you can access it in several ways:

  • From the Start Menu: Your installed distribution will appear as an app in the Start Menu. Clicking on it will open a terminal window connected to your Linux environment.

  • From PowerShell or Command Prompt: You can use the wsl command to launch your default distribution or a specific distribution:

    • wsl: Launches your default distribution.
    • wsl -d DistributionName: Launches a specific distribution (replace DistributionName with the name of the distribution).

  • From Windows Terminal: Windows Terminal (which you can install from the Microsoft Store) provides a modern, tabbed terminal experience that supports multiple shells, including PowerShell, Command Prompt, and WSL. It automatically detects your installed WSL distributions and adds them to the dropdown menu.

Basic Linux Commands: Getting Started

Now that you have a working Linux environment, let’s cover some fundamental Linux commands to get you started:

  • pwd (print working directory): Displays the current directory you’re in.

  • ls (list): Lists the files and directories in the current directory.

    • ls -l: Lists files and directories in a long format, showing permissions, ownership, size, and modification date.
    • ls -a: Lists all files and directories, including hidden ones (those starting with a dot).
    • ls -la: Combines -l and -a.

  • cd (change directory): Changes the current directory.

    • cd /: Navigates to the root directory.
    • cd ~: Navigates to your home directory.
    • cd ..: Navigates to the parent directory.
    • cd path/to/directory: Navigates to a specific directory.

  • mkdir (make directory): Creates a new directory.

    • mkdir new_directory: Creates a directory named “new_directory”.

  • rmdir (remove directory): Removes an empty directory.

    • rmdir empty_directory: Removes the directory named “empty_directory”.

  • rm (remove): Removes files or directories (use with caution!).

    • rm file.txt: Removes the file named “file.txt”.
    • rm -r directory: Recursively removes a directory and its contents (be very careful with this!).

  • cp (copy): Copies files or directories.

    • cp file.txt new_file.txt: Copies “file.txt” to “new_file.txt”.
    • cp -r directory new_directory: Recursively copies a directory and its contents.

  • mv (move): Moves or renames files or directories.

    • mv file.txt new_location/file.txt: Moves “file.txt” to the “new_location” directory.
    • mv file.txt new_name.txt: Renames “file.txt” to “new_name.txt”.

  • touch: Creates an empty file or updates the modification time of an existing file.

    • touch new_file.txt: Creates an empty file named “new_file.txt”.

  • cat (concatenate): Displays the contents of a file.

    • cat file.txt: Displays the contents of “file.txt”.

  • less: Displays the contents of a file one page at a time (useful for large files). Press q to exit.

    • less file.txt

  • head: Displays the first few lines of a file.

    • head file.txt: Displays the first 10 lines of “file.txt”.
    • head -n 20 file.txt: Displays the first 20 lines.

  • tail: Displays the last few lines of a file.

    • tail file.txt: Displays the last 10 lines of “file.txt”.
    • tail -n 20 file.txt: Displays the last 20 lines.
    • tail -f file.txt: Continuously displays the last lines of a file as it’s updated (useful for monitoring log files).

  • grep (global regular expression print): Searches for text within files.

    • grep "pattern" file.txt: Searches for “pattern” in “file.txt”.
    • grep -i "pattern" file.txt: Performs a case-insensitive search.
    • grep -r "pattern" directory: Recursively searches for “pattern” in all files within a directory.

  • sudo (superuser do): Executes a command with elevated privileges (as the root user). You’ll be prompted for your Linux user password. Use this with caution!

    • sudo apt update: Updates the package list (for Debian/Ubuntu-based distributions).

  • apt (Advanced Package Tool) / yum / dnf / pacman: Package managers used to install, update, and remove software. The specific package manager depends on your Linux distribution:

    • Debian/Ubuntu: apt
    • Fedora/CentOS/RHEL: yum (older versions) or dnf (newer versions)
    • Arch Linux: pacman
    • openSUSE: zypper

    Examples (Debian/Ubuntu):
    * sudo apt update: Updates the package list.
    * sudo apt upgrade: Upgrades installed packages.
    * sudo apt install package_name: Installs a package.
    * sudo apt remove package_name: Removes a package.
    * sudo apt autoremove: Removes unused dependencies

  • nano / vim / emacs: Text editors.

    • nano file.txt: Opens file.txt in the nano text editor. Nano is generally considered the easiest for beginners.
    • vim file.txt: Opens file.txt in the vim text editor. Vim has a steeper learning curve but is very powerful.
    • emacs file.txt: Opens file.txt in the emacs text editor. Emacs is another powerful editor with a learning curve.

  • man (manual): Displays the manual page for a command.

  • man ls: Displays the manual page for the ls command.

  • clear: Clears the terminal screen.

This is just a small sample of the many commands available in Linux. As you become more comfortable with the command line, you’ll discover many more useful tools and utilities.

File System Interoperability: Windows and Linux Working Together

One of the most powerful aspects of WSL 2 is the seamless file system interoperability between Windows and Linux.

  • Accessing Windows Files from Linux: Your Windows drives (C:, D:, etc.) are automatically mounted under the /mnt/ directory in your Linux environment. For example, your C: drive is accessible at /mnt/c/. You can navigate to your Windows files and directories using standard Linux commands.

  • Accessing Linux Files from Windows: Your Linux file system is accessible from Windows through a special network share. You can access it by typing \\wsl$\ in the File Explorer address bar, followed by the name of your distribution. For example, \\wsl$\Ubuntu-20.04. You will see the root directory of your Linux distribution. It is generally recommended to modify Linux files from within the Linux environment itself, rather than from Windows, to avoid potential issues with file permissions and line endings.

  • Important Note on File Permissions: Linux uses a different file permission system than Windows. When working with files shared between Windows and Linux, it’s essential to be aware of these differences to avoid permission-related problems. Generally, it is best to manage file permissions within the environment (Windows or Linux) where the file will primarily be used.

Running Linux GUI Applications

While WSL 2 is primarily designed for command-line usage, it is possible to run Linux GUI applications on Windows. There are several ways to achieve this:

  • WSLg (Windows Subsystem for Linux GUI): This is the officially supported method by Microsoft, and it’s the easiest way to run Linux GUI applications. It’s built into newer versions of Windows 11. WSLg provides a seamless experience, allowing you to run Linux GUI applications alongside your Windows applications. It handles the display server, window management, and input devices automatically.

    • Installation: WSLg is usually installed automatically with newer versions of Windows 11. If not, you can install it by ensuring you have the latest Windows updates and WSL 2.
    • Usage: Once installed, you can simply launch a Linux GUI application from your WSL terminal, and it will appear as a window on your Windows desktop. For example:
      bash
      sudo apt install gedit # Install the Gedit text editor (on Debian/Ubuntu)
      gedit & # Launch Gedit in the background

  • X Server (e.g., VcXsrv, Xming): This is an older method that involves installing a third-party X server on Windows. An X server is a program that provides a graphical display environment for Linux applications.

    • Installation: Download and install an X server like VcXsrv (recommended) or Xming.
    • Configuration: Configure your X server (usually involves setting display options and security settings).

    • Usage: Before launching a Linux GUI application, you need to set the DISPLAY environment variable in your WSL terminal:

      bash
      export DISPLAY=:0

      Then, you can launch your GUI application. For example:

      bash
      gedit &

  • Remote Desktop (XRDP): This method involves setting up a remote desktop server (like XRDP) within your Linux environment and then connecting to it from Windows using the Remote Desktop Connection client. This approach is more complex to set up but can provide a more complete desktop experience.

Docker Desktop Integration: Containerization Made Easy

WSL 2 provides a seamless integration with Docker Desktop for Windows. This means you can run and manage Docker containers directly within your WSL 2 environment, leveraging the performance benefits of WSL 2.

  1. Install Docker Desktop for Windows: Download and install Docker Desktop from the official Docker website.
  2. Enable WSL 2 Integration: In Docker Desktop settings, go to “Resources” -> “WSL Integration” and enable integration for your desired WSL 2 distribution.
  3. Use Docker from WSL 2: You can now use the docker command within your WSL 2 terminal to build, run, and manage containers. Docker will use the WSL 2 backend, resulting in significantly improved performance compared to the older Hyper-V backend.

Visual Studio Code Integration: The Ultimate Development Workflow

Visual Studio Code (VS Code), a popular and powerful code editor from Microsoft, offers exceptional integration with WSL 2. This allows you to develop directly within your Linux environment while using the familiar VS Code interface on Windows.

  1. Install VS Code on Windows: Download and install VS Code from the official website.

  2. Install the Remote – WSL Extension: Open VS Code and install the “Remote – WSL” extension from the Extensions Marketplace (Ctrl+Shift+X or Cmd+Shift+X).

  3. Connect to WSL:

    • Click on the green remote indicator button in the bottom-left corner of the VS Code window.
    • Select “Remote-WSL: New Window” (or “Remote-WSL: Reopen Folder in WSL” if you have a folder already open).
    • Choose your desired WSL 2 distribution.

  4. Develop in WSL: VS Code will now open a new window connected to your WSL 2 environment. You can open folders, edit files, run commands, and debug your code as if you were working directly on a Linux machine. VS Code will automatically install a server component within your WSL 2 distribution to enable this seamless integration. All of your extensions will work transparently within the remote WSL environment.

Troubleshooting Common Issues

  • “The Windows Subsystem for Linux optional component is not enabled”: Make sure you’ve enabled the “Windows Subsystem for Linux” optional feature (see Step 1 of the installation guide).

  • “Please enable the Virtual Machine Platform Windows feature”: Make sure you’ve enabled the “Virtual Machine Platform” optional feature (see Step 2 of the installation guide).

  • WSL 2 requires an update to its kernel component: You might see this error if your WSL 2 kernel is outdated. You can update it by running wsl --update in PowerShell as administrator.

  • Network connectivity issues: If you’re having trouble accessing the internet from within your WSL 2 environment, try restarting the WSL service:
    powershell
    wsl --shutdown
    Then, relaunch your distribution. You might also need to configure your network settings within your Linux distribution (e.g., setting up DNS servers).

  • File system performance is slow: If you’re experiencing slow file system performance when accessing Windows files from Linux, try working with files within the Linux file system instead (i.e., not under /mnt/).

  • GUI applications not displaying:

    • Make sure WSLg is installed and enabled if you are using Windows 11.
    • If using an X server, ensure it’s running and that the DISPLAY environment variable is set correctly in your WSL terminal.
    • Check for any error messages in your terminal that might indicate a problem with the display server or the application itself.

  • Error 0x80370102 The virtual machine could not be started because a required feature is not installed: This indicates that virtualization is not enabled in your BIOS/UEFI settings.

  • WslRegisterDistribution failed with error: 0x800701bc / 0x80070003 / 0x80370102: These are common errors that usually relate to problems during installation. Try restarting your machine and re-running the installation steps. Make sure all of the prerequisites (virtualization enabled, features installed) are met.

Advanced Topics

  • Customizing Your Linux Environment: You can customize your Linux environment by installing additional software, configuring your shell (e.g., using Zsh instead of Bash), setting up aliases, and customizing your terminal prompt.

  • Using Multiple Distributions: You can install and run multiple Linux distributions simultaneously with WSL 2. This is useful if you need to work with different environments (e.g., Ubuntu for development, Kali Linux for security testing).

  • WSL Configuration (.wslconfig and wsl.conf): You can customize WSL 2 settings globally using a .wslconfig file in your Windows user profile directory (%UserProfile%) and per-distribution settings using a wsl.conf file within the /etc/ directory of each distribution. These files allow you to configure things like memory limits, CPU limits, swap file size, network settings, and more.

    • .wslconfig (Global Settings):

      • Located in: %UserProfile%\.wslconfig

      • Example:

        ini
        [wsl2]
        memory=4GB # Limit WSL 2 to 4GB of RAM
        processors=2 # Limit WSL 2 to 2 CPU cores
        swap=8GB # Set the swap file size to 8GB
        localhostForwarding=true # Enable localhost forwarding

    • wsl.conf (Per-Distribution Settings):

      • Located in: /etc/wsl.conf (within the Linux distribution)

      • Example:

        “`ini
        [automount]
        enabled = true
        root = /mnt/
        options = “metadata,umask=22,fmask=11”
        mountFsTab = false

        [network]
        generateHosts = true
        generateResolvConf = true

        [interop]
        enabled = true
        appendWindowsPath = true

        [user]
        default = your_username
        ``
        * **        automount:** Controls how Windows drives are mounted.
        * **        network:** Configures network settings.
        * **        interop:** Controls interoperability features between Windows and Linux.
        * **        user`:** Sets the default user.

  • Backing Up and Restoring WSL Distributions: You can back up and restore your WSL distributions using the wsl --export and wsl --import commands.
    * Export: wsl --export <DistributionName> <FileName.tar>
    * Import: wsl --import <DistributionName> <InstallLocation> <FileName.tar>

  • Using Systemd: While WSL 2 doesn’t natively support systemd (the init system used by many modern Linux distributions) out of the box, there are workarounds and third-party tools (like distrod and genie) that allow you to use systemd within WSL 2. This can be useful for running services that rely on systemd.

Conclusion: Embrace the Power of WSL 2

WSL 2 is a game-changer for developers and IT professionals who want to leverage the power of Linux on Windows. Its seamless integration, excellent performance, and full system call compatibility make it a compelling alternative to traditional virtual machines and dual-booting. By following the steps outlined in this article, you can easily install, configure, and start using WSL 2 to enhance your productivity and unlock a world of possibilities. Whether you’re a seasoned Linux user or just starting your journey, WSL 2 provides a powerful and convenient way to bring the best of both Windows and Linux together. Embrace the power of WSL 2 and experience a new level of flexibility and efficiency in your development workflow.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top