# Docker Desktop 4.91 Releases with Containerd Image Store Default and Engine v29 Overhaul

Source: TechNewsList (https://technewslist.com)
Canonical URL: https://technewslist.com/en/article/docker-desktop-4-91-engine-v29-containerd-default-2026-09-15-night
Section: Software (https://technewslist.com/en/software)
Author: TechNewsList
Language: en
Published: 2026-09-15T19:36:46.781+00:00
Updated: 2026-09-15T19:36:46.940896+00:00

> Docker has launched Desktop 4.91 and finalized Engine v29, establishing the containerd image store as the default local runtime for enhanced multi-platform builds.

## TL;DR
- Docker Desktop 4.91.0 makes the containerd image store the default local runtime for all new installations.
- The change replaces the legacy graphdriver architecture with native OCI snapshotter standards used in production Kubernetes.
- Developers gain native multi-platform image management, cryptographic SBOM attestations, and 35% faster Compose startup.
- The legacy overlay2 graphdriver enters formal deprecation ahead of full removal in Docker Engine v30.

## Key points
- Docker Desktop 4.91 officially transitions the containerd image store from experimental status to out-of-the-box default.
- The release unifies local development workstations with standard CNCF and OCI image specifications.
- Multi-architecture container builds (ARM64/AMD64) can now share common base layers without duplicate disk usage.
- Cryptographic software supply chain signatures and SBOM attestations are natively preserved in the local image store.
- Docker Compose receives parallel service dependency boots and distributed cache optimizations.
- Legacy graphdriver storage drivers will be formally retired in Docker Engine v30 scheduled for early 2027.

## What happened

On September 14, 2026, Docker Inc. deployed Docker Desktop 4.91 alongside the milestone release of Docker Engine v29.8, executing the most significant architectural evolution of the local container developer toolchain in nearly a decade. The headline enhancement is the formal transition of the containerd image store from an optional experimental toggle to the default out-of-the-box storage configuration for all new developer installations across macOS, Windows, and Linux.

The transition marks the final retirement phase for Docker's legacy graphdriver storage architecture, standardizing local developer workstations on the same Open Container Initiative (OCI) and Cloud Native Computing Foundation (CNCF) industry standards used in production Kubernetes clusters. The update also bundles substantial performance enhancements to Docker Compose, expanded Buildx multi-platform compilation features, and hardened software supply chain attestation tooling.

## Why it matters

Historically, Docker Engine relied on its proprietary graphdriver subsystem to manage local container image layers, image caches, and container write layers. While effective during the container ecosystem's nascent years, this legacy storage mechanism created acute friction for modern cloud-native workflows. Developers frequently encountered discrepancies between images built locally and those executed within production Kubernetes runtimes, while managing multi-architecture manifests—such as building ARM64 and AMD64 images simultaneously—required awkward workarounds and duplicate disk allocations.

By elevating containerd's native snapshotter architecture to the default local runtime, Docker Desktop 4.91 eliminates these systemic inefficiencies. Developers gain native support for OCI image specifications, enabling multi-platform images to share common base layers seamlessly on disk without duplicated storage footprints. Furthermore, the containerd integration facilitates native cryptographic image signing, Software Bill of Materials (SBOM) generation, and vulnerability attestation storage directly within the local image index, aligning workstation development with modern enterprise cybersecurity mandates.

## Technical details


![Technical breakdown of containerd runtime architecture and OCI image layer execution.](https://rkhynbcsbnkkcwgexzwg.supabase.co/storage/v1/object/public/media/api/1789500998694-voy7xk-docker-desktop-4-91-engine-v29-containerd-default-2026-09-15-night-inside-1-dfec0a648c.webp)


The technical core of the transition lies in containerd's snapshotter plugin interface, which completely replaces the legacy overlay2 storage driver. Snapshotters decouple container image unpacking from filesystem mounting, enabling high-performance differential layer sharing and instant container spin-up times. In Docker Desktop 4.91, the containerd image store is seamlessly integrated with the Docker daemon via internal gRPC endpoints, maintaining full backward compatibility for standard docker run and docker build CLI commands.

The update introduces native support for Wasm (WebAssembly) container shims directly alongside traditional Linux containers, allowing developers to execute high-performance compiled Wasm binaries within standard container composition workflows. Additionally, Docker Compose has been optimized with parallel dependency resolution and distributed build caching, cutting multi-service local environment boot times by up to 35%. The release also patches several low-severity privilege escalation vectors in the desktop virtual machine networking proxy.

## Market / industry impact


![Developer workflow demonstration highlighting multi-platform container builds and local registry syn](https://rkhynbcsbnkkcwgexzwg.supabase.co/storage/v1/object/public/media/api/1789501000152-4144e8-docker-desktop-4-91-engine-v29-containerd-default-2026-09-15-night-inside-2-33060c5482.webp)


The transition consolidates containerd's position as the ubiquitous container runtime foundation across both developer laptops and hyperscale cloud infrastructure. By aligning its desktop runtime directly with CNCF open-source specifications, Docker neutralizes growing competition from alternative desktop container tools such as Podman and Rancher Desktop, which have long promoted their adherence to pure OCI standards.

For enterprise software engineering organizations, the standardization significantly reduces continuous integration pipeline complexity. Build scripts and container images verified locally on developer workstations now behave identically when ingested by production Kubernetes clusters, eliminating the subtle "works on my machine" behavioral discrepancies caused by legacy graphdriver layer serialization. Corporate security teams also benefit from streamlined image scanning, as third-party vulnerability analyzers can inspect native OCI attestations without complex export transformations.

## What to watch next

Docker has announced that existing installations utilizing the legacy graphdriver storage engine will receive automated migration prompts over the coming minor releases, with full legacy driver deprecation scheduled for Docker Engine v30 in early 2027. System administrators managing enterprise developer fleets will evaluate automated migration scripts to ensure legacy custom build plugins transition smoothly to the containerd subsystem.

Developers should also watch for upcoming expansions to Docker's AI toolchain integration. Following the containerd rollout, Docker engineering teams are preparing specialized container templates optimized for local model fine-tuning and GPU passthrough acceleration, bridging the gap between container virtualization and modern artificial intelligence development.

## Sources

- [Docker Documentation Release Notes](https://docs.docker.com/desktop/release-notes/#4910) — Official release notes for Docker Desktop 4.91.0 specifying containerd image store default behavior and Compose updates.
- [Docker Engineering Blog](https://www.docker.com/blog/how-the-containerd-image-store-supercharges-local-development/) — Technical architectural deep-dive into multi-arch emulation, build cache efficiency, and OCI image specifications.
- [The New Stack Cloud Native](https://thenewstack.io/docker-engine-v29-unifies-developer-toolchains-with-native-containerd-support/) — Cloud-native industry analysis evaluating the transition away from the classic graphdriver storage engine.

Mentions: Docker, containerd, Docker Compose, OCI, Cloud Native Computing Foundation

## Sources
- [Docker Documentation Release Notes](https://docs.docker.com/desktop/release-notes/#4910)
- [Docker Engineering Blog](https://www.docker.com/blog/how-the-containerd-image-store-supercharges-local-development/)
- [The New Stack Cloud Native](https://thenewstack.io/docker-engine-v29-unifies-developer-toolchains-with-native-containerd-support/)