Microsoft moved WSL containers to general availability on September 29, with a dedicated CLI, a native API, and enterprise controls. The irony is free; the practical implications for your dev machine are not.

On September 29, Logan Iyer, Corporate Vice President for Windows Platform + Developer, announced that WSL containers are generally available. The feature — shortened to WSLC — shipped as part of WSL 3.0.1, and existing WSL users pick it up with a plain wsl --update. In Microsoft's framing, the Windows Subsystem for Linux is no longer just a way to run Linux distributions on Windows; it now builds and runs Linux containers by itself.

The GA release is really two pieces. The first is wslc.exe, a command-line tool for building, running, and deploying Linux containers directly from Windows. Microsoft also ships container.exe as an alias with the familiar Docker-style verbs, so muscle memory transfers immediately: wslc run --rm -it ubuntu:latest, wslc image ls. Since the public preview, the CLI has gained the boring-but-essential commands — container restart, copying files in and out (wslc container cp), health checks, mount support, configurable storage locations, network connect and disconnect, a wslc system info overview, and a wslc events stream for watching container activity live.

The second piece is the WSL containers API, which lets native Windows applications launch and control Linux containers in code. It ships as a NuGet package with C# and C++/WinRT projections, exposing stdin and stdout, file mounts, networking, and GPU access. Microsoft's pitch for the API is telling: local AI workloads, and cloud-style containerized applications running on a desktop. The container has become the distribution format for AI tooling, and Microsoft wants that format to run on Windows without a Linux VM in the middle.

Ecosystem adoption is already moving. VS Code dev containers can use wslc as their default driver, .NET Aspire treats WSL containers as a container runtime, and community tools — Lazywslc, WSL Container Desktop, the VS Code Container extension — already have integrations out.

Then there is the enterprise angle, which is where WSLC stops being a developer convenience and starts being a fleet feature. Microsoft Defender for Endpoint can surface process, file, and network activity from containers to security teams, and Microsoft Intune can now enable or disable the feature outright and restrict image pulls to approved registries. If your team ships Windows laptops, those two Intune settings are the ones to read first: they turn "developers running arbitrary Linux containers" from a shadow-IT problem into a governed one.

So what does this mean if you live on Linux? A few things worth chewing on. First, the obvious: for a certain class of Windows-based developers, Docker Desktop just became optional. Not replaced — WSLC still lacks Compose support, and Microsoft says it is working on that — but the calculus for a new Windows dev machine changes when the OS itself runs Linux containers. Second, and more interesting: the container runtime market now has the platform vendor shipping its own entry, which puts pressure on everyone else's pricing and feature velocity. Competition from the OS maker is rarely comfortable, but it is usually good for users.

And third, the strategic read: Microsoft is positioning WSL as the home for AI and cloud-native workloads that have traditionally lived on Linux boxes. That is not a small claim. It says the company believes the future of development tooling is Linux-shaped even on Windows desktops — containers, not installers; container run, not setup.exe. Linux won the workload war so completely that the world's largest desktop OS now ships a Linux container runtime as a first-class feature.

The gap to watch is Compose and multi-container orchestration. Until WSLC handles a compose up workflow, Docker Desktop keeps its hold on the serious local-development crowd. But GA releases have a way of growing teeth quickly. If you dual-boot, or you support developers who do, this is worth a test drive: update WSL, run a container, and see how much of your workflow survives without a third-party engine in the middle.

Sources: Windows Developer Blog: WSL containers is now generally available, Sept 29 2026 · BleepingComputer: Microsoft is rolling out Linux container support to WSL · Help Net Security: WSL containers are generally available on Windows · Linuxiac: Microsoft brings native Linux container workflows to WSL