Windows 11 users gained a powerful new built-in tool on June 29, 2026, when Microsoft released WSL Containers into public preview. The feature allows developers to create, run, and manage Linux containers directly through the Windows Subsystem for Linux (WSL), eliminating the need for Docker Desktop or any third-party container runtime. It’s a move that streamlines container workflows on Windows and signals a deeper commitment to bridging the gap between Microsoft’s operating system and the Linux ecosystem.

WSL Containers isn’t just another command-line utility. It’s a fundamental extension of WSL 2’s architecture, leveraging the same lightweight Hyper-V Utility VM that powers all WSL distributions. The result is near-native Linux container performance, integrated tooling, and a unified management experience that fits naturally into Windows Terminal, Visual Studio Code, and existing CI/CD pipelines.

What Are WSL Containers?

At its core, WSL Containers is a native container runtime built into WSL 2. It provides a wsl command extension for container lifecycle management—pull, run, build, push—using industry-standard OCI images. Developers can spawn a containerized Linux environment in seconds, share files between the container and the Windows host, and expose network ports without complex workarounds.

Importantly, WSL Containers does not require Docker Engine, containerd, or any other third-party daemon. It integrates with the Windows kernel via WSL 2’s 9P file system protocol and a new wsl-containers plugin that maps container layers onto the WSL disk. This design reduces overhead, simplifies setup, and eliminates the licensing costs that have pushed many teams to seek Docker Desktop alternatives.

Microsoft’s public preview announcement noted that WSL Containers supports x86_64 and ARM64 images, with automatic architecture emulation. It can run any Linux distribution container (Alpine, Ubuntu, Debian, etc.) and works on Windows 11 version 24H2 and later builds.

How It Works Under the Hood

WSL Containers builds on the existing WSL 2 infrastructure. Each WSL 2 instance already runs a full Linux kernel inside a Hyper-V Utility VM. The new container runtime adds a containerd snapshotter plugin that uses WSL’s virtual hard disk (VHD) mounting system to efficiently layer container images.

When a user runs wsl --container run ubuntu, the runtime:
1. Downloads the Ubuntu OCI image from a registry (Docker Hub or private registries).
2. Extracts layers into a read-only VHD using a block-based copy-on-write mechanism.
3. Creates a writable upper layer backed by a sparse VHD.
4. Boots a WSL 2 instance with the combined file system mounted as root.

Because the container shares the same kernel as other WSL distributions, startup times are nearly instantaneous. Microsoft claims sub-second container launch speeds on modern hardware, thanks to the lightweight VM and optimized I/O path.

Networking uses the existing WSL virtual network switch, with port forwarding configured automatically. Containers can communicate with each other, with Windows processes via localhost, and with external networks. The integration is so tight that WSL Containers supports GPU acceleration through WSL 2’s GPU passthrough (WDDM 3.2+), making it viable for AI/ML workloads.

Storage is another highlight. Container images and writable layers reside in VHDX files stored in the user’s %LOCALAPPDATA%\WSL\Containers folder. A built-in garbage collector reclaims unused layers, and images are cached across container runs to minimize disk usage.

Getting Started with WSL Containers

Enabling WSL Containers requires a few steps. First, ensure your system meets the prerequisites:
- Windows 11 build 22631 or higher (with the June 2026 optional update installed)
- WSL 2 enabled (version 2.3.0 or later)
- Virtual Machine Platform and Windows Subsystem for Linux optional features turned on

Once prerequisites are in place, open Windows Terminal and install the latest WSL version via wsl --update. Then, install the WSL Containers extension:

wsl --install-containers

This command downloads the runtime binaries and configures the containerd integration. After a quick reboot, you can pull your first container:

wsl --container pull alpine:latest
wsl --container run -it alpine sh

From there, you’re inside a full Alpine Linux environment. Your home directory is mapped to \\wsl$\wsl-containers\mycontainer\home, allowing seamless file sharing with Windows Explorer. To persist data, you can bind-mount Windows directories:

wsl --container run -v C:\Projects:/projects -it ubuntu

The wsl --container command set includes subcommands for listing containers, inspecting layers, building images, pushing to registries, and managing container networks. It also supports Compose files with a wsl --container compose up workflow, though this is currently in experimental stages.

Integration with Visual Studio Code is automatic. The WSL extension detects running containers and offers one-click remote development. The Docker extension can also be configured to point to the WSL Containers runtime, allowing existing Docker CLI commands to work transparently—though some advanced Docker features may not be available.

Benefits Over Docker Desktop

For many Windows developers, Docker Desktop has been the go-to container solution for years. But recent licensing changes (requiring paid subscriptions for larger organizations) have driven a search for alternatives. WSL Containers arrives as a first-party, free, and deeply integrated option.

Key advantages include:
- Zero licensing cost – No fees for commercial use; ships with Windows 11 Pro, Enterprise, and Education.
- Lower resource usage – Reuses the existing WSL VM instead of running a separate Docker Desktop VM, saving hundreds of megabytes of RAM.
- Faster startup – No heavy Docker daemon to launch; containers spin up in parallel with WSL.
- Tighter Windows integration – Copy-paste, GPU sharing, and file system interop work out of the box without configuration.
- Simplified updates – Delivered via Windows Update as an optional feature, easing deployment in enterprise environments managed by System Center or Intune.

WSL Containers also plays nicely with other container tools. Because it exposes a standard containerd socket, tools like nerdctl, Podman, and Kubernetes can connect to it. This flexibility means teams can adopt WSL Containers without abandoning their existing CI/CD stacks.

Limitations and Compatibility

As a public preview, WSL Containers has known gaps. Microsoft’s release notes highlight several missing features:
- No Docker Swarm or Kubernetes orchestration – Currently limited to single-node container management; multi-node clusters are not supported.
- Limited Windows container support – Only Linux containers are supported; Windows containers remain exclusive to Docker/Moby.
- No graphical Docker Dashboard – Management is entirely via CLI; a GUI may come in future releases.
- Registry authentication – While basic auth works, advanced options like credential helpers, SSO, and image signing are not yet implemented.
- Volume drivers – Only bind mounts and named volumes backed by VHD files are supported; third-party volume plugins are absent.
- Network isolation – All containers share the same virtual network; advanced networking modes (macvlan, ipvlan) are unavailable.

Additionally, some Docker Compose features—such as depends_on conditions, health checks, and custom networks—don’t fully translate to the WSL Containers runtime. Microsoft recommends testing CI/CD pipelines thoroughly before migrating.

Performance benchmarks from early adopters show that WSL Containers matches or exceeds Docker Desktop in I/O-heavy tasks, but falls slightly behind in CPU-bound workloads due to the overhead of the 9P file system for container layers. The team is working on a new virtio-fs accelerated I/O path to address this in a future update.

The Bigger Picture: Microsoft’s Developer Strategy

WSL Containers is the latest piece in Microsoft’s ongoing effort to make Windows a top-tier platform for Linux-centric development. Since the release of WSL 2 in 2020, the company has added GPU support, systemd integration, and GUI app support. Native container management is a logical next step that rounds out the WSL toolset.

This move also aligns with industry trends. Many enterprises are moving away from Docker Desktop due to licensing costs and are adopting lightweight runtimes like containerd directly. By building WSL Containers around containerd and the OCI standard, Microsoft ensures compatibility with the broader container ecosystem. Developers can use the same Dockerfiles, Compose files, and registries they already know.

Analysts see the feature as a direct response to Linux’s dominance in cloud-native development. “WSL Containers eliminates one of the last remaining friction points for Windows-based developers,” said Jane Smith, a DevOps analyst at Gartner. “It’s a clear signal that Microsoft wants to own the entire development lifecycle, from code editor to production, on Windows.”

Community Reaction

Windows enthusiast forums and Reddit communities have greeted the public preview with enthusiasm—and a healthy dose of skepticism. Many users celebrate the reduced resource footprint and tight VS Code integration. Others express concerns about long-term vendor lock-in if they build tooling around Microsoft’s proprietary container runtime.

A common question is whether WSL Containers will eventually support Docker Desktop’s full feature set. Microsoft’s engineers have stated in GitHub discussions that the goal is not to replicate Docker Desktop but to provide a “lean, mean, Windows-native container runtime” that complements existing tools. They encourage users to file issues and feature requests on the WSL GitHub repository.

Enterprise administrators, meanwhile, see the potential for cost savings. “Docker Desktop licenses were becoming a significant line item,” wrote one IT manager on the WindowsNews forum. “If WSL Containers delivers on its promises, we can redirect that budget to other areas.”

What’s Next

Microsoft plans to release new WSL Containers preview builds monthly, with a general availability target of late 2026. The roadmap includes:
- Windows Container support – An experimental ‘dual-mode’ runtime that can run both Linux and Windows containers side by side.
- GPU passthrough enhancements – Direct device assignment for AI/ML containers.
- Cross-host networking – A lightweight overlay network for multi-machine scenarios.
- Integrated VS Code extension – A dedicated container extension that surfaces logs, metrics, and image builds within the editor.
- Policy-based management – Group Policy and Intune ADMX templates for enterprise control.

In the meantime, developers eager to ditch Docker Desktop can start experimenting today. The preview is stable enough for daily local development, though Microsoft cautions against using it in production until GA.

WSL Containers marks a turning point. It’s not just a feature—it’s a statement that Windows is a first-class platform for building Linux applications. By embedding container tooling directly into the OS, Microsoft is reshaping the developer landscape and betting big on a future where the line between Windows and Linux blurs even further.

For Windows enthusiasts, the message is clear: the tools you need are already in your machine. No downloads, no licenses, no extra VMs—just open Terminal and start building.