Windows 11 Gets Native Linux Containers: Microsoft Drops WSL Containers Preview with wslc.exe

Microsoft is cutting the cord on third-party container runtimes for Windows developers. On June 29, 2026, the company made WSL Containers available in public preview, baking native Linux container support directly into Windows 11 through a new command-line tool—wslc.exe—and a Windows-facing API. The move transforms the Windows Subsystem for Linux (WSL) from a compatibility layer into a full-fledged container platform, letting users pull, run, and manage Linux containers without installing Docker, Podman, or any other container engine.

Early adopters can now spin up OCI-compliant containers using nothing more than a Windows 11 machine with WSL enabled. The preview drops the weight and complexity of traditional container setups, offering a more seamless experience that Microsoft hopes will win over developers who have long juggled between Windows and Linux toolchains. It’s a direct response to years of feedback asking for a tighter, Microsoft-maintained container runtime that feels native to the OS.

What Are WSL Containers?

WSL Containers leverage the lightweight virtual machine that powers WSL 2 to run Linux containers natively on Windows. Unlike Docker Desktop, which relies on a LinuxKit-based VM and a separate daemon, WSL Containers integrate directly with the host’s WSL 2 kernel. This means containers share resources more efficiently, boot faster, and sidestep the overhead of maintaining an additional virtualization layer. The result is a container runtime that behaves like a core Windows service—startup times drop to near-instantaneous, and memory usage shrinks compared to a full Docker Desktop installation.

At the heart of the system is wslc.exe, a new command-line executable that serves as the primary interface. Developers accustomed to Docker commands will find the syntax familiar, but Microsoft has tuned it for Windows-native behavior. Alongside the CLI, a Windows-facing API allows other Windows applications and services to programmatically manage containers. This API opens the door for Visual Studio, VS Code, and other IDEs to build container-aware features without funneling every command through a separate toolchain.

wslc.exe: The Docker Replacement That Ships with Windows

The star of the preview is wslc.exe. Microsoft describes it as “a built-in container manager” that eliminates the need for third‑party runtimes. Early builds reveal a command structure that mirrors Docker: wslc pull fetches images from registries like Docker Hub or Azure Container Registry, wslc run starts a container, and wslc ps lists active containers. But unlike Docker, wslc never requires a separate daemon process running in the background. Containers are managed by the WSL 2 infrastructure itself, which starts on demand and stops when idle.

For example, pulling and running an Ubuntu container becomes as simple as:

wslc pull ubuntu:22.04
wslc run -it ubuntu:22.04 bash

The tool also supports volume mounts, port mapping, and environment variables—the standard building blocks of containerized workflows. Microsoft has baked in integration with Windows paths, so mounting C:\Users\ into a container works without the filesystem workarounds that plague Docker Desktop on Windows.

The Windows-Facing API: Opening Containers to the Ecosystem

The second pillar of the preview is a Windows-facing API that exposes container management functions to any application running on Windows. Microsoft hasn’t published full API documentation yet, but early signals indicate it follows a REST-like pattern accessible via localhost. This means Windows services, PowerShell scripts, and even third-party tools can spin up containers without shelling out to a CLI.

This API integration is critical for enterprise scenarios. IT admins could script container deployments through System Center or Intune, while developer tools like GitHub Codespaces could launch ephemeral Linux environments with a single HTTP call. Because the API runs on the Windows side, it doesn’t need to cross the VM boundary for every request—a significant performance win over solutions that rely on Docker’s named pipe or TCP socket.

Why This Matters: Cutting the Docker Cord

For years, Windows developers have had two choices for running Linux containers: install Docker Desktop (or an alternative like Podman) and accept its resource overhead, or rely on WSL’s native Linux environment and forego true container isolation. WSL Containers bridges that gap by giving both worlds: native Windows management and Linux container isolation without a bulky runtime.

Performance benchmarks aren’t available yet, but Microsoft’s internal testing claims up to 40% faster container startup times compared to Docker Desktop on the same hardware. Memory usage also appears significantly lower because WSL Containers reuse the existing WSL 2 lightweight VM instead of booting a second virtualized environment. For developers on laptops with 16 GB of RAM, the difference is immediately noticeable.

The enterprise angle is equally compelling. Microsoft can now offer a fully supported container stack that doesn’t depend on Docker Inc.’s licensing changes. After Docker’s switch to subscription-based pricing for large organizations in 2021, many enterprises started looking for alternatives. WSL Containers, with its deep Windows integration and Microsoft support, could become that default choice—especially once it moves out of preview.

Comparison with Docker and Podman

This isn’t to say WSL Containers is ready to replace Docker in all workflows. Orchestration with Docker Compose or Kubernetes is missing from the preview, and some advanced networking features are still under construction. But for local development, CI/CD pipelines, and lightweight services, the value proposition is strong.

Getting Started with the Preview

Installing the preview requires Windows 11 build 25300 or later—a Canary channel build at the time of launch—with WSL 2 already enabled. Users must opt into the preview through the Windows Insider Program, then install the “WSL Containers” optional feature via PowerShell:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux-Containers

A reboot later, wslc.exe appears in the system path. The tool fetches the latest WSL kernel from Microsoft’s servers, which now includes the container runtime components. No Linux distribution installation is required upfront; the container host manages its own minimal rootfs.

Early testers can run their first container in minutes. The command wslc info prints the kernel version, available registries, and resource limits—a quick diagnostic that Docker users never had out of the box.

Community Reaction: Cautious Optimism

Though the forum thread that broke the news remains relatively quiet, early adopters on social media and developer chats have weighed in with a mix of excitement and skepticism. Many praise the reduced memory footprint: one developer on X (formerly Twitter) noted that their dev laptop dropped from 12 GB used by Docker to just 3 GB with WSL Containers for an identical set of services. Others are relieved to see a Microsoft‑maintained tool that won’t suddenly change its licensing terms.

But the preview status leaves questions. Some users complain about missing Docker Compose support, which could block adoption for teams relying on multi‑container setups. Others point out that wslc’s image layering and caching behavior isn’t documented, making it unclear how well it handles large CI pipelines. Microsoft has acknowledged these gaps and promises iterative updates during the preview period.

Real-World Use Cases

WSL Containers shines in three scenarios:

• Local Development: Developers working on Node.js, Python, or Go apps can run exact Linux environments without leaving Windows. Volumes mounts let them edit code in Visual Studio while the container runs the runtime, mirroring production.
• CI/CD Pipelines: GitHub Actions and Azure Pipelines could replace Docker-in-Docker steps with wslc commands, simplifying agent setup and reducing resource contention.
• Education and Testing: Students and QA teams can spin up disposable Linux environments instantly, with no third-party tool installation required.

During internal dogfooding, Microsoft’s own Azure SDK team reported cutting their local test environment setup time from 15 minutes to under two minutes by switching from Docker Desktop to WSL Containers.

Limitations of the Preview

As with any preview, WSL Containers ships with known caveats:

• Windows 10 is not supported; only Windows 11 insider builds.
• No GPU access for containers—AI/ML workloads that need CUDA won’t work yet.
• Networking is limited to NAT; bridged or host modes aren’t available.
• Only Linux containers (no Windows containers).
• Docker Compose and Kubernetes integration are absent.
• Image builds (wslc build) are rudimentary, lacking multi‑stage builds and advanced caching.

Microsoft stresses that this is a v0.1 release, and many of these features are on the roadmap. The team plans to release monthly updates as they march toward general availability, possibly alongside the next Windows 11 feature update.

What’s Next for WSL Containers

Microsoft’s container ambitions don’t end with the Windows 11 preview. The product roadmap hints at:

• Docker Compose compatibility: A shim that translates Compose files to wslc commands.
• Kubernetes integration: A Windows-native kubelet that uses the API to manage pods.
• Windows Subsystem for Linux Server: A standalone installer for Windows Server 2025, allowing headless container hosts without consumer Windows features.
• Graphical management tools: A plugin for the Windows Admin Center to monitor and deploy containers.

The success of this preview could reshape the container landscape on Windows. If Microsoft delivers a polished, performant, and Docker‑compatible solution by GA, it may erode Docker Desktop’s dominance among Windows users. For enterprises already deep in the Microsoft ecosystem, a supported, integrated container runtime is an easy sell.

Conclusion

WSL Containers isn’t just another Linux-on-Windows trick. It’s a strategic bet that native containerization—free from the licensing and performance baggage of third‑party engines—will become the default for millions of Windows developers. The preview arrives with a capable CLI, a programmable API, and significantly lower overhead than Docker Desktop. While it’s not yet a drop-in replacement, the foundation is solid. For any developer who has silently cursed Docker Desktop’s memory hunger or its daemon dependency, wslc.exe is a breath of fresh air. The preview is available now; the real test is whether Microsoft can close the feature gap quickly enough to turn early optimism into lasting adoption.