
Microsoft shipped a native Linux container runtime for Windows at Build 2026. The tool is called wslc, it lives inside WSL, and it does the one thing Windows developers have been paying Docker Desktop to do for years. Public preview arrives by end of June. If you run Docker Desktop purely for local containers on Windows, wslc is about to give you a free, zero-install alternative.
What WSL Containers Actually Is
WSL Containers is not a Docker Desktop clone. It ships as a standard WSL update and comes in two parts: a CLI (wslc.exe) and a programmable API that lets Windows applications spin up Linux containers as part of their own logic. The CLI uses OCI-compatible images — the same ones you pull from Docker Hub today — and its command structure will look familiar immediately:
# Run a container interactively
wslc run --rm -it ubuntu:latest bash
# Map a port
wslc run -p 8080:80 nginx:latest
# GPU passthrough for AI/ML workloads
wslc run --gpus all nvidia/cuda:12.2.0-base-ubuntu22.04 nvidia-smi
# List running containers
wslc container ps
# Build an image from a Dockerfile
wslc build -t myapp:latest .
The API side — exposed via wslcsdk.dll, with WinRT and C# bindings — is aimed at tooling developers. IDEs, CI agents, and developer platforms on Windows can now orchestrate Linux containers programmatically without requiring Docker Desktop to be installed at all.
The Architecture Is Better Than Docker Desktop’s
Docker Desktop runs every container inside a single shared virtual machine. WSL Containers takes a different approach: each Windows application using the API gets its own dedicated lightweight VM, with separate storage, networking, and resources, backed by Hyper-V isolation. For enterprise security teams, per-app isolation means a compromised container in one context cannot affect containers in another. For AI/ML developers, WSL Containers exposes the host GPU via CDI — same principle as Docker’s GPU support, minus the Docker daemon.
WSL Containers vs Docker Desktop
| Feature | WSL Containers | Docker Desktop |
|---|---|---|
| Cost | Free | $9–$24/user (commercial) |
| Install required | No (standard WSL update) | Yes |
| Isolation model | Per-app VM | Shared VM |
| GPU support | Yes (CDI) | Yes (NVIDIA) |
| Docker Compose | Not at launch | Yes |
| GUI | No | Yes |
| Enterprise management | Windows policies / MDM | Docker Business |
What It Does Not Do Yet
Docker Compose is not included at launch. If your workflow depends on multi-container orchestration via compose.yml, WSL Containers is not ready to replace Docker Desktop today. There is no GUI — this is CLI-first. It also requires Windows 11, given the Hyper-V dependency. Preview status means rough edges are guaranteed, and the official Microsoft documentation is sparse at this stage — typical for a feature entering public preview. Check the Docker Desktop pricing page if you want a concrete sense of what you would be moving away from.
When and How to Get It
WSL Containers enters public preview by end of June 2026 as a standard WSL update. No separate download, no new installer — just keep WSL updated and wslc.exe will arrive automatically. Enterprise teams get policy-based controls out of the box: IT admins can restrict which image registries are allowed, enable or disable the feature via MDM or Group Policy, and audit what containers are running on developer machines using existing Windows tooling. That enterprise management story is directly aimed at organizations paying for Docker Business primarily to get governance features.
The Bigger Picture
Apple shipped a native Container CLI for macOS at WWDC 2025. Microsoft is doing the same for Windows in 2026. Both moves have the same subtext: platform vendors want to own the container runtime layer rather than cede it to a third party. Docker Desktop is not going away — its Compose support, GUI, Docker Scout integration, and extension ecosystem give it real staying power. But for developers who only run Docker Desktop because they need docker run, wslc run is about to be a free, zero-install replacement with stronger isolation. That is a meaningful shift, and the Build 2026 announcement is the starting line — not the finish.













