Linux News · Windows · Cloud-Native Development
Microsoft Brings Native Linux Container Support to WSL
Microsoft has made WSL Containers generally available, bringing a built-in command-line interface and programmatic API for Linux container workflows to the Windows Subsystem for Linux (WSL). The release gives developers a more direct way to build, run, and manage Linux containers on Windows, while adding networking controls, container monitoring, configurable storage, and enterprise management features.
Announced on September 29, 2026, WSL Containers introduces
wslc.exe and its container.exe alias. The feature
is intended to simplify local development for Linux-based applications,
cloud-native projects, and certain AI workloads without requiring a separate
container platform for every use case. See the
official Microsoft announcement.
- WSL Containers is generally available, with the built-in
wslc.exeCLI. - Developers can run Linux containers and manage images, networking, mounts, and container lifecycles.
- A WSL Container API enables Windows applications to control containers programmatically.
- Microsoft has expanded integration with Defender for Endpoint and Intune for enterprise governance.
- Compose support is still a stated work-in-progress, so existing Docker-based workflows may still need Docker or another compatible runtime.
What Is WSL Containers?
The Windows Subsystem for Linux lets developers run a Linux environment alongside Windows. WSL Containers extends that experience with container management built into WSL itself. Containers package applications and their dependencies so they can run in more consistent environments across development and testing systems.
The new workflow is designed to reduce setup friction for developers who want to use Linux containers while continuing to work from Windows terminals, editors, and applications. Microsoft documents the feature in its WSL Containers technical documentation.
What Is New in the General Availability Release?
1. Native container CLI
Use wslc.exe to run containers, manage images, inspect workloads, and perform common container tasks from Windows.
2. Container lifecycle management
New capabilities include restart operations, file copying, configurable stop timeouts, mounts, and container health checks.
3. Networking and storage
Connect or disconnect containers from networks, configure network drivers, and select a storage location for the default session.
4. Monitoring and enterprise controls
Real-time event streams and integrations with Microsoft security and management tools help organizations oversee container activity.
How the WSL Container CLI Works
The wslc.exe interface provides commands for common container
tasks. Microsoft also documents container.exe as an alias.
The following examples are based on Microsoft’s published getting-started
documentation.
Step 1: Update WSL
Open PowerShell and update WSL to obtain the latest available version. Microsoft’s documentation specifies WSL version 2.9.3 or later for the WSL Containers feature; verify the current requirements before deployment.
wsl --update
wsl --versionStep 2: Run a temporary Ubuntu container
This command starts an Ubuntu container, prints a message, and removes the container after the command finishes.
wslc run --rm -it ubuntu:latest bash -c "echo Hello world from WSL container!"Step 3: Start an NGINX web server
The following example runs NGINX in the background and maps port 8080 on the Windows host to port 80 in the container.
wslc run -d --rm -p 8080:80 --name web nginxTest the published port from PowerShell:
curl http://localhost:8080Step 4: Inspect and stop the container
wslc container list
wslc container stop webThese examples are for learning and local testing. Check the official documentation for current command syntax, supported options, and troubleshooting guidance before using the CLI in automated workflows.
Official tutorial: Get started with containers on WSL.
WSL Container API: Running Containers From Windows Applications
WSL Containers also provides an API for developers building native Windows applications that need to work with Linux containers. Instead of requiring users to manage every container operation manually, an application can programmatically pull images, create and control containers, exchange process input and output, configure mounts and networking, and access supported GPU functionality.
Microsoft publishes the Microsoft.WSL.Containers NuGet package
for its documented API projections. For example, a .NET developer can add
the package with:
dotnet add package Microsoft.WSL.ContainersReview the API’s current support status and platform requirements before building a production application. Microsoft notes that the C++/WinRT projection is still in preview in its documentation.
Enterprise Security and Management
Native container workflows are useful only when organizations can govern how they are used. Microsoft has added enterprise-oriented controls for WSL Containers, including management options through Intune and visibility into container process, file, and network activity through Microsoft Defender for Endpoint, subject to product prerequisites and supported configurations.
| Capability | Why it matters |
|---|---|
| Intune policy controls | Administrators can control access to WSL Containers and restrict image pulls to approved registries. |
| Defender for Endpoint | Supported deployments can expose container activity to security teams for investigation and monitoring. |
| Network configuration | Additional network controls can help developers work across varied local and enterprise network environments. |
| Configurable storage | Teams can choose a storage location suited to their available disks and development environment. |
Organizations should validate their WSL version, licensing, endpoint onboarding, registry policies, and security configuration before adopting the feature broadly. Start with Microsoft’s Defender for Endpoint WSL guidance and Intune settings for WSL.
Networking and Performance Improvements
Microsoft says WSL Containers can deliver up to twice the performance when
accessing Windows files from Linux environments. The release also introduces
a consomme networking mode intended to improve compatibility
across developer and enterprise scenarios.
These figures and improvements are Microsoft’s reported results, not a guarantee that every workload will experience the same performance. Actual outcomes depend on file access patterns, storage, network setup, security software, and application behavior. Benchmark your own workload before making performance claims or changing production architecture.
Does WSL Containers Replace Docker Desktop?
Not for every developer or team. WSL Containers creates a built-in option for common container tasks, but the best choice depends on existing tooling and application requirements.
| Consideration | WSL Containers | Docker-based workflow |
|---|---|---|
| Getting started | Uses the WSL update and built-in CLI workflow. | Typically requires installing and configuring a container runtime. |
| Windows integration | Designed for direct integration with WSL and Windows applications. | Offers established integrations through Docker Desktop and related tooling. |
| Compose projects | Compose support is on Microsoft’s roadmap, not a current equivalent to assume. | Docker Compose is established for multi-container application workflows. |
| Best fit | Developers exploring native WSL container workflows and supported integrations. | Teams dependent on Compose, existing Docker tooling, and mature workflows. |
Microsoft has identified Compose support as a major requested addition and
described plans to support existing compose.yaml files through
a future workflow. Until that support is available and suitable for your
use case, teams relying on Compose should retain a compatible runtime.
Who Should Consider WSL Containers?
- Developers: Build and test Linux applications from a Windows workstation.
- DevOps engineers: Explore container workflows and local testing without adding a separate platform for every task.
- .NET developers: Investigate embedding Linux container operations into Windows applications through the API.
- AI developers: Evaluate local containerized workloads, including supported GPU scenarios.
- IT and security teams: Assess policy enforcement and security visibility for managed development endpoints.
How to Get Started
- Check your current WSL installation with
wsl --version. - Update WSL using
wsl --update. - Read Microsoft’s official WSL Containers documentation and verify prerequisites.
- Test a simple container in a non-production environment.
- Review networking, image registry, storage, and security requirements before rolling it out to a team.
Start here: Microsoft Learn — WSL Container · WSL releases on GitHub · Microsoft’s general availability announcement.
Related Articles on VMoreCloud
Explore more guides and news related to Linux, virtualization, cloud infrastructure, and Windows administration:
- Linux tutorials and news — Linux distributions, tools, and open-source developments.
- Virtualization guides — Explore virtualization concepts and infrastructure workflows.
- Cloud computing articles — Browse cloud technologies, services, and administration guides.
- Windows Server tutorials — Explore Windows infrastructure and administration topics.
Internal-link note: verify these category URLs on your live VMoreCloud site. Replace any URL that does not exist with the closest relevant published category or article. Avoid leaving links that lead to 404 pages.
Official Sources and Further Reading
- Microsoft Windows Developer Blog: WSL Containers is now generally available
- Microsoft Learn: WSL Container
- Microsoft Learn: Get started with containers on WSL
- Microsoft Learn: Defender for Endpoint WSL plug-in
- Linuxiac: Microsoft Brings Native Linux Container Workflows to WSL
Editorial note: This article summarizes Microsoft’s published announcements and technical documentation. Command examples are adapted from official documentation; this article does not claim independent benchmark testing. Feature availability and requirements can change as WSL evolves.