If you work in development, you know that setting up a Linux environment on Windows has always been a bit cumbersome or dependent on external tools that can sometimes be too large. Well, Microsoft has made a game-changer with WSL Containers , a feature that allows us to manage Linux images and containers natively, without having to go through the hoops of Docker Desktop or its complicated enterprise licenses.
This tool is not a simple update, but a paradigm shift in how Windows handles virtualization. By integrating the ability to run containers directly into the Windows Subsystem for Linux , the goal is to create a much smoother workflow, eliminating unnecessary layers and allowing developers to focus on writing code without wrestling with operating system configuration.
What exactly are WSL Containers?
Simply put, this is a new WSL capability that allows you to create and launch Linux containers without needing an external daemon. At its heart is wslc.exe , a command-line interface designed to be intuitive, especially if you're already familiar with Docker, as the commands are very similar. In fact, to avoid any confusion, Microsoft has included an alias called container.exe.
But it's not all about the console. They've also released a WSL container API available via a NuGet package. This is pure gold for those who develop native Windows applications (using C#, C++, or C) and want their program to manage Linux containers internally, handling input/output (stdin/stdout), network mounts, or even direct GPU access for AI tasks with PyTorch.
Key differences with Docker Desktop
Many will wonder if this replaces Docker Desktop. The short answer is that, in many cases, yes. While Docker typically uses a single, shared Linux virtual machine for everything, WSL Containers launch independent Hyper-V micro-VMs for each container. This means that each process has its own memory and storage budget, preventing one container from "spying" on another and improving security.
Another crucial point is cost. Docker Desktop requires payment for large companies, while WSL containers are included with Windows 11 at no extra cost. However, there's an important detail: you need Windows 11 Pro, Enterprise, or Education , as the Home version doesn't support the Hyper-V isolation necessary for all of this to work.
How to get it up and running step by step
If you want to start experimenting, the first thing to do is make sure you have WSL version 2.9.3 or later. Since it's still in preview, you'll need to open a terminal as administrator and run the command `wsl --update --pre-release` . Once updated, you can enable the feature by running `wsl --install-feature containers`.
To check that everything is in order, simply type wslc versionIf you want to launch your first container without complications, try with wslc run --rm hello-worldYou'll see the image download automatically and display the greeting, confirming that the system is operational. From here, you can use commands like wslc container ps to see what's alive or wslc image ls to review your local images.
Creating your own images and optimizing the workflow
If you want to take this to the next level, the ideal solution is to use Visual Studio Code with the WSL extension. To create your own image, you need a file called a Containerfile (very similar to a Dockerfile) and to consult good programming books to structure your app. For example, if you're building a Django app, you would define the Python image, copy the requirements, and expose port 8000.
The compilation process is simple: you use wslc build -t your-app-name . and then you launch it with wslc run -d -p 8000:8000 --name mi-app nombre-de-tu-appThe most powerful thing is that you can integrate this into MSBuild or CMake, making container creation part of your project's build process.
Performance, Networking, and Storage
Microsoft hasn't just scratched the surface. They've implemented virtiofs as the default file system, which significantly speeds up data transfer between Windows and Linux, eliminating that annoying bottleneck of slow mounts. Furthermore, there's an experimental network mode called consomme , which is a boon for those working in corporate environments, as it resolves typical conflicts with enterprise VPNs by routing traffic more intelligently.
Regarding resource management, the system is more aggressive in releasing memory to the host. Since they are lightweight virtual machines, when you stop a container, memory is recovered faster than in the monolithic model. To keep the disk clean, don't forget to use wslc container prune y wslc image prune to delete what you no longer use.
This technology represents a significant leap forward by integrating containerization directly into the Windows 11 core, allowing developers to eliminate third-party software and optimize performance through Hyper-V isolation and the virtiofs system. With the arrival of the wslc.exe CLI and VS Code compatibility, a robust, free, and efficient environment is established that simplifies running Linux workloads, although a professional edition of Windows is required to fully leverage its capabilities.