● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement is rolling out.
KubeEra
D

Docker (Wasm)

Wasm
Open source · Apache-2.0

Docker (Wasm) is Docker's integration layer for running WebAssembly workloads through the standard Docker CLI and Docker Engine/Desktop — docker run against Wasm modules instead of (or alongside) OCI container images, using containerd shims

updated 2026-07-01

What it is

Docker (Wasm) is Docker's integration layer for running WebAssembly workloads through the standard Docker CLI and Docker Engine/Desktop — docker run against Wasm modules instead of (or alongside) OCI container images, using containerd shims (WasmEdge, wasmtime, Spin, etc.) under the hood. Official upstream description is not publicly available, so treat this as based on the visible repo signals: Go codebase, Apache-2.0, active release cadence.

It's not a Wasm runtime itself — it's the plumbing that lets Wasm modules slot into the container workflow teams already have (Dockerfiles, docker run, docker buildx, registries).

Who builds it and why

Primarily Docker, Inc., with community contribution (280 contributors on GitHub is a healthy, non-trivial number for infra tooling). The motivation is straightforward: Wasm is gaining traction for lightweight, fast-starting, sandboxed workloads (edge, serverless, plugin systems), and Docker doesn't want that traffic to bypass its tooling and registries entirely. This is Docker defending its position as the default interface for shipping workloads, not a from-scratch bet on Wasm as a category.

CNCF maturity: not publicly available — this sits outside CNCF's formal process; it's a vendor-driven feature/project rather than a foundation-governed one.

Production readiness signal

  • 37,690 GitHub stars — strong community interest/visibility.
  • Last commit 2026-06-30 — actively maintained, not abandoned.
  • 280 contributors — real, distributed engineering effort, not a single-vendor side project in practice even if Docker leads it.
  • Latest release v5.2.0 — mature version numbering suggests iterative stability work, not a v0.x experiment.
  • License Apache-2.0 — standard permissive open-source license, no copyleft friction.

What's missing from public data: founding date, an official description, and CNCF maturity status. If you're doing vendor due diligence, get Docker to confirm SLA/support posture directly — don't assume enterprise support parity with core Docker Engine just because the brand is attached.

Who should use this

  • Teams already standardized on Docker tooling who want to experiment with Wasm workloads without introducing a second toolchain.
  • Edge/IoT teams needing fast cold-starts and small footprints where full OCI containers are overkill, but who still want familiar CI/CD and registry workflows.
  • Platform teams evaluating Wasm as a plugin/sandboxing mechanism (e.g., extending an app with untrusted third-party modules) who want to prototype fast.

Who should NOT use this

  • Anyone running Wasm in production today for anything beyond edge/serverless niches — the Wasm ecosystem (WASI, networking, threading) is still catching up, and Docker's integration inherits those gaps.
  • Teams not already on Docker — if you're on containerd or CRI-O directly, going through Docker's layer adds an unnecessary dependency; use the shims directly.
  • Kubernetes-native shops needing Wasm at the orchestration layer — look at runwasi + containerd shims directly, or Spin/SpinKube, instead of routing through Docker Desktop tooling.
  • Anyone needing hard multi-tenant security guarantees today — Wasm sandboxing is promising but the surrounding tooling (this included) hasn't had the adversarial scrutiny that OCI/runc has after a decade in production.

Alternatives

  • Spin / SpinKube (Fermyon) — purpose-built Wasm application framework and Kubernetes runtime, more opinionated and Wasm-native than Docker's bolt-on approach.
  • containerd + runwasi shims directly — skip Docker entirely and wire Wasm runtimes into containerd yourself if you're already Kubernetes/containerd-native.
  • WasmEdge / wasmtime standalone — run Wasm modules without any container tooling at all, useful if you don't need OCI-compatible packaging.

Pricing

Fully open source (Apache-2.0). The tooling itself is free. Note that Docker Desktop — often the delivery vehicle for this feature — has its own separate commercial licensing for larger organizations; that's a Docker Desktop policy question, not a Wasm-integration one.

Frequently asked

What is Docker (Wasm)?+
Docker (Wasm) is Docker's integration layer for running WebAssembly workloads through the standard Docker CLI and Docker Engine/Desktop — docker run against Wasm modules instead of (or alongside) OCI container images, using containerd shims (WasmEdge, wasmtime, Spin, etc.) under the hood.
Who builds Docker (Wasm)?+
Primarily Docker, Inc., with community contribution (280 contributors on GitHub is a healthy, non-trivial number for infra tooling).
Is Docker (Wasm) production ready?+
37,690 GitHub stars — strong community interest/visibility. Last commit 2026-06-30 — actively maintained, not abandoned. 280 contributors — real, distributed engineering effort, not a single-vendor side project in practice even if Docker leads it. Latest release v5.2.
Who should use Docker (Wasm)?+
Teams already standardized on Docker tooling who want to experiment with Wasm workloads without introducing a second toolchain. Edge/IoT teams needing fast cold-starts and small footprints where full OCI containers are overkill, but who still want familiar CI/CD and registry workflows.
Who should not use Docker (Wasm)?+
Anyone running Wasm in production today for anything beyond edge/serverless niches — the Wasm ecosystem (WASI, networking, threading) is still catching up, and Docker's integration inherits those gaps.
What are the alternatives to Docker (Wasm)?+
Spin / SpinKube (Fermyon) — purpose-built Wasm application framework and Kubernetes runtime, more opinionated and Wasm-native than Docker's bolt-on approach. containerd + runwasi shims directly — skip Docker entirely and wire Wasm runtimes into containerd yourself if you're already Kubernetes/containerd-native.
How much does Docker (Wasm) cost?+
Fully open source (Apache-2.0). The tooling itself is free. Note that Docker Desktop — often the delivery vehicle for this feature — has its own separate commercial licensing for larger organizations; that's a Docker Desktop policy question, not a Wasm-integration one.