Skip to main content

Docker Engine 29.10.0

Release Date: November 16, 2026

Docker has published Docker Engine 29.10.0, released on November 16, 2026, a release that moves the Engine API specification to OpenAPI 3.2, changes how loopback registries are treated when insecure registries are configured, and adds experimental support for daemon-managed jobs.

What Changed

The headline item is a potential breaking change for local registry workflows. If insecure-registries is explicitly set in daemon.json or passed through --insecure-registry, the daemon no longer automatically treats loopback addresses (127.0.0.0/8 and ::1/128) as insecure. Pulls and pushes to local registries over plain HTTP or with untrusted certificates can therefore start failing after an upgrade until those addresses are added to the list.

When insecure-registries is omitted entirely, loopback registries remain insecure by default. Setting an empty array disables all default insecure registries.

The Engine API specification now uses OpenAPI 3.2 as its source format in api/openapi.yaml. A Swagger 2.0 spec generated from it is still published for existing tooling, and this release also carries a Swagger 2.0 copy pinned to API v1.57. Future API versions will not get per-version Swagger 2.0 copies, so tooling that reads those files needs to move to the OpenAPI 3.2 documents.

Packages are now available for AlmaLinux, Oracle Linux, and Rocky Linux, broadening the set of supported RPM distributions.

New Features

  • Experimental jobs: one-shot and cron-scheduled workloads managed natively by the daemon, opt-in through the built-in extension org.mobyproject.jobs.v0, enabled with --enable-extension.
  • containerd configuration directory: the embedded containerd can be customized with files in /etc/docker/containerd.d/.
  • Restarting attribute on die events: event consumers can now tell when a container is going to restart instead of guessing from exit codes.

Fixes and Enhancements

  • Obsolete socket families are blocked in the default AppArmor and seccomp profiles.
  • The containerd image store no longer reports an empty image when docker image inspect or docker image ls runs on a host whose platform was not pulled from a multi-platform image.
  • The CLI no longer waits for the telemetry export timeout when the OTLP endpoint refuses connections.
  • docker cp no longer prints a success message when the copy fails.
  • docker manifest annotate accepts platforms outside its predefined list, such as linux/loong64.
  • docker ps no longer prints an empty NAMES column when every container name contains a slash.
  • The daemon no longer deletes the docker0 interface on restart when a user-managed bridge and default-address-pools are configured.
  • Windows layer exports with NTFS sparse files are fixed.
  • JSON streaming errors now include HTTP status codes.
  • Image selection on ARM64 Linux hosts prefers the highest variant supported by the CPU.
  • Duplicate GPU counts are rejected consistently when shorthand and explicit options are mixed.

Packaging

The release bundles BuildKit v0.35.0 and runc v1.5.3 in static binaries, and updates the Go runtime to 1.27.4.

Why It Matters

The loopback registry change is the item most likely to bite in CI. Any pipeline that pushes to a registry on localhost over HTTP needs either a trusted certificate or an explicit entry such as localhost:5000 in the insecure registry configuration. The jobs extension also sets up the daemon to host scheduled workloads directly, a capability Docker Compose 5.8.0 starts to use.

What Is Next

Expect the Swagger 2.0 fallback to disappear in a future API version, and watch the jobs extension as it graduates from opt-in status. Distributions carrying their own Engine builds will take a few weeks to catch up with 29.10.0.

Other Versions

We use cookies for ads and analytics.