# The end of the Linux monopoly: Microsoft integrates Containers into Windows to retire Docker

> Microsoft keeps pressing the accelerator and this time announces the launch of WSL Containers, to compete with Docker and Podman
> By José Maldonado · Technology · 2026-07-03

For more than a decade, modern software development has lived under an undisputed axiom: **containers belong to the world of Linux**. If you are a developer working on Windows, your day-to-day involved an uncomfortable truce, depending on third-party abstraction layers such as Docker Desktop to be able to package, test and deploy your applications in local environments.

However, this has just suffered a silent but devastating earthquake. Microsoft has officially presented **WSL Containers** (based on the new integrated tool wslc.exe). This technology does not simply seek to compete on the periphery of virtualization; it seeks to wrest the monopoly of local development infrastructure from traditional intermediaries and position Windows 11 at the absolute epicenter of global software innovation.

## The origin of the project: The bridge that became a destination

To understand how we got here, we must recall the birth of [**WSL (Windows Subsystem for Linux)**](https://learn.microsoft.com/en-us/windows/wsl/install). What began in Redmond as a timid experiment to allow the execution of basic Bash commands on Windows quickly evolved into WSL2, a robust architecture that ran a real Linux kernel inside a hyper-optimized lightweight virtual machine.

**[VS Code, Microsoft's pawn that became the editor of the digital world](https://observatorioblockchain.com/en/technology/como-usar-vs-code-el-rey-indiscutible-del-desarrollo-de-software/)**

Despite the success of WSL2, containers still required external tools to manage the underlying engine. This dependence on third-party software generated friction, performance problems and, above all, headaches in the corporate environment due to changes in the licensing policies of the major platforms.

But it was at the recent [**Microsoft Build 2026**](https://news.microsoft.com/build-2026/), conference where the tech giant decided to reveal its long-term game: **equipping Windows with the native ability to build, run and orchestrate Linux containers without installing absolutely anything else**. The launch in Public Preview at the end of June 2026 marks the beginning of a new era: **containers are now part of the fabric of the Windows operating system.**

## Why is Microsoft betting on this technology?

Microsoft's strategy goes far beyond offering a friendly alternative to independent developers; it is a masterstroke of technological sovereignty, talent retention and enterprise integration. By internalizing containers, Redmond seeks to break external dependencies and consolidate Windows 11 as the definitive operating system for software engineering.

## Elimination of licenses and commercial friction in the corporate environment

In the fabric of large corporations, managing third-party software is not just a technical matter, but a legal and financial maze. When the dominant commercial tools in the container sector changed their licensing policies to require paid subscriptions from companies of a certain size, they introduced enormous friction. Organizations were forced to audit thousands of workstations, manage unforeseen budgets and deal with compliance departments.

![If you have done development on Windows, you will know Docker Desktop...and you will hate it.](https://content.observatorioblockchain.com/wp-content/uploads/2026/07/docker-desktop-421_f2-1110x653-1.avif)
*If you have done development on Windows, you will know Docker Desktop…and you will hate it.*

Microsoft has identified a golden opportunity here. By integrating container management directly into the operating system's native command-line interface (CLI), it transforms a tool that previously required intermediaries into a standard feature of the system. For CTOs (Chief Technology Officers) and system administrators, this represents an automatic enterprise-ready solution:

1.  Licensing costs per seat for external tools are eliminated.
2.  Software deployment is unified across corporate laptop fleets through traditional Windows group policies.
3.  Security risks associated with the third-party software supply chain are mitigated, since all lifecycle support for the container engine is handled by Microsoft itself.

## The container as system infrastructure, not as an isolated application

Until now, tools such as Docker Desktop or Podman worked as software "islands". They were monolithic applications that had to start up, update and maintain their own daemons and network configurations on top of Windows. If the engine hung or the underlying virtual machine lost synchronization, the developer's workflow stopped completely.

By turning the container engine into a fundamental piece of the Windows architecture through the wslc.exe binary, Microsoft changes the rules of the game: the container ceases to be an application and becomes pure, transparent infrastructure.

## The real Trojan horse for the hybrid AI era

The launch of the wslc.exe command line is only the surface of the ecosystem. The truly disruptive element and the definitive blow to the competition is the publication of the native container API for WSL, immediately accessible through NuGet distribution packages for key languages such as C, C++ and C#.

This is not a simple addition for web developers; it is an infrastructure designed for the next decade of hybrid software and Artificial Intelligence. Thanks to this API, Windows will now allow:

1.  Any Windows software developer can program a traditional desktop application (.NET, WinUI) and have it, underneath, invisibly invoke microservices, databases or optimized processes that only exist inside an isolated Linux container. The end user will only see a clean Windows interface, without knowing that the magic happens in a native Linux container in the background.
2.  Build processes can be fully automated; you can program your workflow so that, when compiling your app, a container is spun up, runs complex unit tests in an isolated Linux environment, and is destroyed upon completion, all integrated into Microsoft's native build tools.
3.  At a time when local language models (LLMs) and on-device AI are exploding, the API allows packaging complex Machine Learning and computer vision pipelines (taking advantage, for example, of CUDA scripts on latest-generation GPUs) inside standardized containers. Any Windows application can consume these models locally, quickly and securely, isolating the heavy Python or AI library dependencies from the host operating system.

![API integration demonstrated in Visual Studio Code](https://content.observatorioblockchain.com/wp-content/uploads/2026/07/wslc-api.webp)
***API integration demonstrated in Visual Studio Code***

## Advantages over Docker on Windows

But what does this mean for the developer? Well, the competitive advantages of this new technology are certainly drastic:

1.  Minimal memory footprint: There are no heavy graphical interfaces running permanently in the background consuming gigabytes of RAM. The service starts and suspends efficiently along with the subsystem.
2.  Integration with MSBuild and CMake: Developers can write a couple of lines in their project configuration files so that the container is built, runs CUDA scripts (with direct access to latest-generation NVIDIA Blackwell architecture GPUs) and is deployed automatically as part of the native Windows app build cycle.
3.  Terminal universality: Being a direct executable in the Windows PATH, it works in any console environment natively without complex virtual network socket configurations.

**[TIDAL will stop paying royalties for music generated entirely with AI](https://observatorioblockchain.com/ia/tidal-dejara-de-pagar-regalias-por-la-musica-generada-con-la/)**

## Step by step: How to install and test WSL Containers today?

Since the technology is currently in Public Preview (with a view to its General Launch in autumn 2026), it is necessary to enable the WSL pre-release channel. Follow these steps to set it up on your Windows 11 machine:

## Step 1: Update to the pre-release version

Open a PowerShell or Windows Terminal window with Administrator privileges and run the update command pointing to the experimental channel:

wsl --update --pre-release

Let the system finish downloading and installing the latest packages directly from Microsoft's development servers.

## Step 2: Restart the subsystem

To ensure the new binaries are correctly injected into the architecture, completely shut down the active WSL instances:

wsl --shutdown

Close your current terminal and reopen a new standard window.

## Step 3: Verify the wslc installation

Check that the new native container engine is available in your system path by running:

wslc version

You can also use the simplified alias:

container --version

## Step 4: Run your first native container

To put the system to the test, run the classic community test container. The system will take care of downloading the image automatically if it does not exist in your local environment:

wslc run --rm hello-world

If everything has been configured correctly, you will see the welcome message on screen running completely natively on the new Windows infrastructure. To go one step further and deploy an interactive Ubuntu console, simply type:

wslc run --rm -it ubuntu:latest bash

![A look at Windows Containers and its cross-system integration](https://content.observatorioblockchain.com/wp-content/uploads/2026/07/wslc-cli.webp)
***A look at Windows Containers and its cross-system integration***

With the launch of WSL Containers, Microsoft makes clear that it is no longer content to be a complacent spectator in the modern development ecosystem. By absorbing containerization capabilities directly into the core of Windows tools, it redefines the rules of the game. The battle against Docker and Podman has begun, but the real prize Redmond is pursuing is to turn Windows into the definitive, self-sufficient and indispensable platform for software engineers around the world.
