WSL Containers Is Now Generally Available for Windows Developers

Microsoft has made WSL Containers generally available, opening its container tooling for Windows Subsystem for Linux to all developers rather than restricting it to a preview channel. According to reporting by Neowin, the feature is now open to everyone, which is a meaningful milestone for Windows developers who build or run containerized applications.

Reaching general availability signals that Microsoft now considers the tooling stable enough for everyday use. For anyone who has been waiting to adopt container workflows on Windows without the usual setup overhead, this is the point where the platform is effectively telling you it is ready.

What WSL Containers actually does

WSL Containers lets you run Linux containers directly inside the Windows Subsystem for Linux. Rather than standing apart from WSL, the feature rides on the same WSL 2 infrastructure that already powers your Linux distro on Windows, including the lightweight utility virtual machine that WSL 2 uses to host a real Linux kernel.

The practical effect is that if you are developing a containerized workload, whether it is a microservice, a Docker-based pipeline, or a cloud-native app, you can build, run, and test those containers without leaving your WSL environment. You are not forced to layer a separate container engine or a full Linux virtual machine on top of everything else.

Developers can now build and run containers without leaving their WSL environment.

What general availability changes

When Microsoft ships a feature in preview, it is essentially a test track. Developers are invited to try it, file bugs, and give feedback, but it is not the version you would point at production work. Moving WSL Containers to general availability means the tooling has graduated past that stage.

That does not imply every possible edge case is resolved, but it does mean Microsoft has run the feature through its testing and now recommends it as the standard option. For teams evaluating container tooling for Windows, this is the signal that WSL Containers has moved from experimental to production-ready.

What this means for you

For Windows developers who work with containers, the biggest change is a reduction in friction. Historically, running Linux containers on Windows meant juggling Docker Desktop, a WSL backend, and occasionally a separate Linux VM just to get things working. WSL Containers is positioned to simplify that stack by giving you a single, integrated path for container work.

If you are already comfortable with WSL, you can lean on one toolchain instead of stitching together multiple products. That matters for anyone who has spent time troubleshooting why a container engine will not play nicely with their WSL setup.

How to get it

Because WSL Containers is part of the WSL platform, the first step is making sure your WSL installation is current. From Windows PowerShell or Command Prompt, you can check for and install WSL updates with the wsl --update command, then restart the subsystem with wsl --shutdown.

Once your WSL build is up to date, the container tooling is available. From there, you will typically reach it through the container runtime of your choice, whether that is Docker, Podman, or another engine compatible with your distro. Check your distro’s package manager for the runtime you want to use, and you should be able to start building and running containers.

An abstract visualization of stacked translucent containers with a Linux flag and Docker-style whale icon, floating in a — Container tooling now runs on the same WSL 2 infrastructure that powers Linux distros.

The bigger picture

WSL Containers fits into Microsoft’s broader push to make container development seamless across its platforms. With heavy investments in Azure container services such as Azure Kubernetes Service and Azure Container Instances, giving Windows developers a first-class way to build and run containers locally aligns with that strategy.

WSL itself launched in 2016 and reached production with WSL 2 in 2019, and features like this continue to widen what the platform can do natively on Windows. For now, the general availability release is primarily about stability and confidence, and it gives developers a cleaner, more integrated route to container work than the patchwork of tools that came before.

Source: Neowin

Over to you: Are you switching your container workflow over to WSL Containers, or sticking with Docker Desktop?