WSL Containers: Build and Run Linux Workloads on Windows

Post Views: 6

WSL containers now enable execution of Linux workloads on Windows systems.

Introduction to WSL Containers

WSL containers now enable execution of Linux workloads on Windows systems. This functionality addresses the need for developers to manage cloud-native applications, AI processing, and testing environments without relying on third-party tools. The feature was introduced at Microsoft Build 2026 and is currently available in the public preview phase of the Windows Subsystem for Linux, specifically version 2.9.3.

Activation Methods

Users can activate the containers by executing the command wsl –update –pre-release or by installing the dedicated component. The implementation includes two core elements.

Core Components

Linux Container Command-Line Utility

The first is the Linux container command-line utility, wslc.exe, which integrates into the system path after an update. This tool maintains compatibility with existing container commands, allowing developers to launch a Linux desktop within a container, execute CUDA scripts to verify GPU functionality, and perform development tasks using the same interface. An alternative command, container.exe, provides equivalent functionality.

Container API Integration

The second component is an API that enables Windows applications to execute Linux containers as part of their operations. Microsoft provides a NuGet package for this integration, supporting programming languages such as C, C++, and C#. This allows native Windows applications to leverage Linux codebases, deploy cloud-native applications locally, and restrict Linux processes to specific host resources. The API supports integration with MSBuild and CMake, enabling developers to embed container build and deployment steps directly into project configurations.

Enterprise Management Features

Microsoft’s documentation includes detailed guides and sample code, while a session at Build 2026 demonstrated practical use cases. Enterprise management features have been extended to include Microsoft Defender for Endpoint, which now monitors Linux container activity. Administrators can configure policies through Intune, controlling access to WSL distributions and containers. These settings include registry allowlists to restrict image sources, addressing a common organizational requirement. Current support for Group Policy Objects and ADMX templates will soon be complemented by Intune dashboard integration.

Visual Studio Code Integration

Visual Studio Code’s dev containers now support wslc, requiring users to adjust the Docker Path setting in dev container configurations. This feature is slated for general availability in future releases.

Technical Enhancements

Underlying technical enhancements include the adoption of a new default file system, virtiofs, which improves Windows file access speeds by 100%. A novel networking mode, consomme, routes Linux network traffic through Windows, ensuring Linux applications inherit host-level networking configurations, security policies, and enterprise connectivity. Memory management has also been optimized, with unused resources returned to the Windows host in a scheduled manner. These improvements are initially available within WSL containers but are planned for broader implementation across the WSL ecosystem.

Future Plans and Availability

Container platforms such as Docker Desktop, Podman Desktop, and Rancher Desktop benefit from these advancements, offering Windows users high-performance alternatives. The feature remains in the pre-release channel, with a target general availability date in the fall of 2026. Technical details include the ability to run Linux desktops in containers, validate GPU access via CUDA, and integrate container workflows into existing development pipelines. Enterprise users gain control over container registries and distribution access, while performance optimizations address file system and networking bottlenecks.