Business & policy

docker on windows is about to become obsolete, and wsl containers are why

At a glance:

  • Docker Desktop will become obsolete as WSL Containers replace it on Windows.
  • WSL Containers run each container in its own Hyper‑V VM, improving isolation and security.
  • Docker Compose support is missing at launch, but other features like GPU acceleration across Intel, AMD, and Nvidia are available.

WSL containers: the new standard for Windows developers

Windows Subsystem for Linux (WSL) has long been a favorite for running Linux tooling without leaving Windows. The latest update brings native Linux container support, meaning developers can launch containers directly inside WSL without installing a separate Linux distribution. This removes the need for Docker Desktop, the long‑standing third‑party application that has bundled Docker Engine, a GUI dashboard, and a shared utility VM.

Because WSL containers are built into the Windows operating system, they receive updates automatically with every Windows patch cycle. The integration also eliminates the overhead of maintaining a separate Docker Desktop installation, streamlining the developer workflow and reducing the attack surface associated with a separate application.

Security advantages over Docker Desktop

Docker Desktop runs all containers inside a single shared utility VM, sharing the same kernel, storage, and networking stack. This shared environment can be a security risk: a compromised container can potentially affect the entire stack, and the free home edition lacks the allowlisting and other controls that Docker Business licenses provide.

WSL containers, by contrast, create a dedicated Hyper‑V VM for each container. Each VM has its own storage, networking, and resource allocation, and no shared Docker Engine or kernel. This isolation means that a container that becomes infected with malware cannot touch other containers or the host, and developers can run containers as rootless by default, a feature that Podman also offers.

Missing features and trade‑offs

One of the main limitations of WSL containers at launch is the absence of Docker Compose support. Compose is essential for running multi‑container applications and for sidecar patterns such as Tailscale sidecars that the author uses for networking. Until Microsoft adds Compose, users will need to manage containers manually or rely on third‑party tools.

The Docker Desktop GUI dashboard, widely criticized for being bloated and poorly organized, is also gone. Users who previously relied on Portainer or similar management interfaces will need to adjust to command‑line management or alternative GUIs. Docker Scout, a monitoring tool, has no WSL equivalent, but Windows Defender may scan container images before they are enabled, offering a different form of security oversight.

GPU acceleration beyond Nvidia

Docker on Windows is limited to Nvidia GPU pass‑through, a significant drawback for developers needing hardware acceleration. WSL removes this restriction: it supports the following GPU backends:

  • Arm (Mali)
  • Nvidia (CUDA)
  • AMD (ROCm)
  • Intel (OpenVINO)
  • Rockchip (RKNN)

With this breadth, GPU‑accelerated machine‑learning tasks that previously required a Linux or WSL2 environment can now run on any supported GPU. The Immich container, a popular self‑hosting image library, can leverage these backends for faster processing, and other ML workloads benefit from the same flexibility.

Developer transition and next steps

The author, a long‑time XDA contributor, expresses enthusiasm for dropping Docker Desktop in favor of WSL Containers. He notes that WSL’s performance is superior to older Layer‑2 hypervisors and that integration with the Windows desktop eliminates awkward key combinations for copy‑and‑paste.

The transition will involve a learning curve: users will need to adapt to new commands and potentially re‑architect multi‑container setups without Compose. However, Microsoft’s roadmap suggests that Compose support will arrive relatively quickly, and the long‑term benefits—simpler management, tighter isolation, and broader GPU support—make the switch a compelling move for Windows developers.

Editorial SiliconFeed is an automated feed: facts are checked against sources; copy is normalized and lightly edited for readers.

FAQ

What is the main reason Docker Desktop is becoming obsolete on Windows?
Docker Desktop is being phased out because Windows Subsystem for Linux (WSL) now provides native Linux container support, eliminating the need for the separate Docker Desktop application and its shared utility VM. WSL containers run each container in its own Hyper‑V VM, offering improved isolation and automatic updates with Windows.
How do WSL Containers improve security compared to Docker Desktop?
WSL Containers create a dedicated Hyper‑V VM for each container, giving each container its own storage, networking, and resources. This isolation means a compromised container cannot affect other containers or the host, and developers can run containers rootless by default—unlike Docker Desktop, which runs all containers in a single shared VM and lacks the allowlisting features of Docker Business licenses.
Will Docker Compose be supported in WSL Containers?
At launch, WSL Containers do not include Docker Compose support, which is essential for multi‑container orchestration and sidecar patterns like Tailscale. Microsoft is expected to add Compose support in a future update, but until then users will need to manage containers manually or use third‑party tools.

More in the feed

Prepared by the editorial stack from public data and external sources.

Original article