Docker Desktop isn’t dead. But for the first time since 2016, the case for paying for it has gotten specific enough to write down.

Within three weeks in June 2026, Apple and Microsoft both shipped free native container alternatives. On June 9, Apple released Containers 1.0 at WWDC, a Swift-native runtime that gives every container its own lightweight VM, runs arm64 workloads at near-native speed, and uses Rosetta 2 for amd64 emulation instead of Docker’s QEMU layer. On June 29, Microsoft shipped WSL Containers in public preview, a daemonless runtime built into WSL 2.9.3 that runs Linux containers on Windows 11 without Docker Desktop or any third-party tool.

Both cost nothing. Both share one critical gap: neither includes Docker Compose support.

That’s not a footnote. That’s the whole story.

The wrong take

The “Docker is dead” narrative has been circulating since Docker introduced commercial licensing in 2022. It resurfaced with every post about WSL Containers last week. The argument: Apple and Microsoft have shipped free container runtimes, so why would anyone keep paying $15/user/month for Docker Desktop?

The answer is in the GitHub discussion for Apple’s project. The request for Compose support has 678 upvotes and Apple’s response at a WWDC workshop was direct: the team is small, focused on foundational components, and Compose is high on the list with no timeline attached. Microsoft’s launch note for WSL Containers was equally plain: “Docker Compose is not included at launch.”

Nobody who depends on a docker-compose.yml file can switch today. Most engineering teams depend on exactly that.

What Docker’s moat actually is

Docker Desktop’s value was never the container runtime. Containerd runs on Linux without any Docker product. OrbStack, the macOS alternative at $8/user/month, already beat Docker on performance using Rosetta 2 instead of QEMU well before Apple built the same thing natively. The runtime has been a commodity for years.

Podman makes this point even sharper. The Red Hat-backed daemonless runtime has been free since 2019, is rootless by default, and has supported podman compose for three years. On macOS it runs via podman machine — a Linux VM under the hood, same as Docker Desktop. For teams doing straightforward multi-service development and willing to accept a rougher macOS experience and incomplete devcontainer support, Podman is a viable switch today with no licence required. If you haven’t evaluated it, that’s worth a morning.

What Docker actually sells is the orchestration layer. Compose for multi-service local environments, devcontainer integration for VS Code and GitHub Codespaces, Docker Scout for image scanning, Testcontainers Cloud for integration test environments, and the GUI dashboard that non-CLI engineers actually use. That’s what makes a Docker Desktop Team license at $15/user/month ($1,800 a year for a 10-person team) defensible as a line item.

Strip those out and you’re paying for a VM wrapper. There’s no case for paying for a VM wrapper in 2026.

The architecture difference that actually matters

The one-VM-per-container model in Apple Containers is worth understanding because it’s architecturally cleaner than Docker’s shared-kernel approach, and the security story is better. A container escape has to beat a hypervisor boundary, not just Linux namespaces. That’s the same isolation model Firecracker and Kata Containers sell in multi-tenant clouds.

On the Windows side, WSL Containers runs without the persistent background daemon Docker Desktop requires: each container gets its own Hyper-V-isolated environment, and the wslc CLI mirrors Docker commands closely enough that existing muscle memory transfers.

Both are technically interesting. Neither closes the Compose gap.

When the math changes

Apple Containers requires macOS 26 (Tahoe), which is in developer beta now with GA expected this autumn. WSL Containers has monthly preview builds planned with a general availability target of late 2026. Apple acknowledged Compose as a priority at WWDC; Microsoft’s roadmap is monthly wslc preview builds through to GA.

Realistic window for basic Compose parity (multi-container orchestration from a compose.yml, not the full Docker Compose feature set) is probably H1 2027, though it could move. If you want to cut the Docker Desktop bill right now on macOS, OrbStack already runs Compose at $8/user/month and doesn’t require a beta OS.

The decision your team should make now

If your local dev environment runs one service per engineer and doesn’t touch Compose or devcontainers, the math has already changed. Move to Apple Containers when Tahoe ships, or WSL Containers on Windows 11 today, and cancel the Docker Desktop subscription.

If your team uses docker-compose.yml for local development, the math hasn’t changed yet. It will, within 12 months. The right move now is to audit what you’re actually getting from Docker Desktop: Compose, devcontainers, Scout, the extension ecosystem, the GUI? That answer tells you exactly when your license becomes optional and what the migration looks like.

Most teams have never had this conversation because Docker Desktop sat below the threshold of scrutiny. Two free native alternatives shipping within three weeks of each other is a good reason to put it on the agenda before the next renewal.

If you want help running that audit, talk to us.

Sources