On this page · 8 sections
  1. Loopback registries lose their insecure default when insecure-registries is set
  2. Engine API 1.57 and the move to OpenAPI 3.2
  3. Experimental jobs for one-shot and cron-scheduled workloads
  4. Restarting attribute on container die events
  5. Customising embedded containerd and new distribution packages
  6. Upgrade checklist for Docker Engine 29.10.0
  7. Also in this release
  8. Sources

TL;DR

Docker Engine 29.10.0 no longer treats loopback registries (127.0.0.0/8 and ::1/128) as insecure by default once you configure insecure-registries explicitly, so pulls and pushes to local HTTP or untrusted-TLS registries can fail after the upgrade. Hosts that never set insecure-registries keep the old loopback default. The same Moby release notes for 29.10.0 raise the Engine API to version 1.57, move its specification to OpenAPI 3.2 and add experimental jobs support. Anyone running local registries or tooling that reads the Swagger files should review this before upgrading.

ChangeWho is affectedAction
Loopback registries lose their insecure default when insecure-registries is setUsers who explicitly configure insecure-registries or --insecure-registry and use local registries over HTTP or untrusted TLSBreaking: add only the required addresses, such as localhost:5000, to insecure-registries, or configure TLS with a trusted certificate
Engine API specification in OpenAPI 3.2Tooling that depends on api/swagger.yaml or the per-version Swagger 2.0 copyChange (marked as a warning in the API v1.57.0 notes): plan the move to api/openapi.yaml
Experimental jobsOperators who want daemon-managed one-shot or cron-scheduled workloadsNew: opt in with --enable-extension org.mobyproject.jobs.v0
Restarting attribute on die eventsConsumers of GET /eventsNew: read the restarting attribute on container die events
Customising embedded containerdOperators who need to configure the embedded containerdNew: place configuration files in /etc/docker/containerd.d/

Loopback registries lose their insecure default when insecure-registries is set #

“Docker Engine no longer automatically treats loopback addresses ( 127.0.0.0/8 and ::1/128 ) as insecure registries.” Moby release notes for 29.10.0

The change applies when you set insecure-registries in daemon.json or pass --insecure-registry. In that case pulls and pushes to local registries that use HTTP or untrusted TLS certificates may fail unless those registries are listed. The release notes give two options: configure TLS with a trusted certificate, or add only the required local addresses, such as localhost:5000, to your existing insecure registry configuration.

JSON
{
  "insecure-registries": ["localhost:5000"]
}

If insecure-registries is omitted, loopback registries remain insecure by default. Setting "insecure-registries": [] in daemon.json disables all default insecure registries, so the loopback default no longer applies on that host. The pull request behind the change (moby/moby#53868) adds that the default can't be switched off from the command line, because the --insecure-registry flag does not accept an empty value, so the empty list works only in daemon.json.

JSON
{
  "insecure-registries": []
}

The same pull request aligns the embedded containerd with this setting. Containerd allowed HTTP for localhost registries on its own, based on the hostname or loopback address. The daemon now overrides that fallback when Docker considers the registry secure, while an explicit containerd host configuration is preserved. A daemon that already sets insecure-registries should therefore be checked for every local registry it serves.

Engine API 1.57 and the move to OpenAPI 3.2 #

The release raises the Engine API version to 1.57 (moby/moby#53972). The specification now uses OpenAPI 3.2 as its source format, in api/openapi.yaml. A Swagger 2.0 specification generated from it is still published in api/swagger.yaml for existing tooling, and the release includes a Swagger 2.0 copy pinned to API v1.57 in api/docs/v1.57-swagger.yaml, as the Moby release notes for 29.10.0 describe. Future API versions won't get a per-version Swagger 2.0 copy, so tooling that reads these files needs to move to the OpenAPI 3.2 files.

The API v1.57.0 release notes mark the same migration (moby/moby#53630) as a warning and list a separate schema fix. The ImageManifestSummary.ImageData schema listed UnpackedSize as required, although that field doesn't exist, and the unpacked size is reported in Size.Unpacked (moby/moby#53750). Any client generated from the old schema should read the size from Size.Unpacked.

Experimental jobs for one-shot and cron-scheduled workloads #

Jobs run one-shot and cron-scheduled workloads that the daemon manages natively. The Moby release notes for 29.10.0 describe it as an experimental, opt-in built-in extension, enabled with --enable-extension org.mobyproject.jobs.v0 (moby/moby#53485). Without that flag the extension is not enabled, so hosts that do not need scheduled workloads take no action for this feature.

Restarting attribute on container die events #

Container die events from GET /events now include a restarting attribute, set to "true" when the container is about to restart, either from its restart policy or from a manual restart, as the API v1.57.0 release notes state (moby/moby#50908). The attribute is omitted when the container won't restart, including during daemon shutdown. The attribute announces the restart but doesn't guarantee it, because the restart can still be cancelled or fail, so event consumers should treat it as a signal rather than a commitment.

Customising embedded containerd and new distribution packages #

The Moby release notes for 29.10.0 add support for customising Docker's embedded containerd with configuration files in /etc/docker/containerd.d/ (moby/moby#53946). The same notes state that Docker Engine packages are available for AlmaLinux, Oracle Linux, and Rocky Linux.

Upgrade checklist for Docker Engine 29.10.0 #

  1. Before upgrading, open daemon.json and check for an insecure-registries key and for any --insecure-registry flag on the daemon command line.
  2. For each local registry that uses HTTP or an untrusted TLS certificate, add only its address, such as localhost:5000, to insecure-registries, or configure TLS with a trusted certificate.
  3. Upgrade to Docker Engine 29.10.0.
  4. After upgrading, run pulls and pushes against each local registry to confirm they still succeed.
  5. Plan to move tooling that reads api/swagger.yaml or api/docs/v1.57-swagger.yaml to api/openapi.yaml, since later API versions get no per-version Swagger 2.0 copy.
  6. To try jobs, start the daemon with --enable-extension org.mobyproject.jobs.v0.

Also in this release #

  • Security profiles: obsolete socket families are blocked in the default AppArmor and seccomp profiles (moby/moby#54093). The profile update names AX.25, IPX, AppleTalk, NET/ROM, ROSE, Econet, ATM SVC, IrDA, WANPIPE, ISDN and CAIF, and removes DECnet from the seccomp socket allowlist.
  • Images: the containerd image store no longer reports an empty image when the host platform is not pulled (moby/moby#54040); ARM64 Linux hosts prefer the highest image variant they support (moby/moby#53910); Windows layer exports with NTFS sparse files are fixed (moby/moby#53745).
  • CLI: docker <unknown-command> --version reports an unknown command error (docker/cli#7408); docker cp no longer prints "Successfully copied" when the copy fails (docker/cli#7515); docker manifest annotate accepts platforms such as linux/loong64 (docker/cli#7448); docker ps shows names when all of a container's names contain a slash (docker/cli#7481); docker manifest annotate gains shell completion for --os and --arch (docker/cli#7449); duplicate GPU counts are rejected consistently (docker/cli#7312); the CLI no longer waits for the telemetry export timeout when the OTLP endpoint refuses connections (docker/cli#7495).
  • Daemon and packaging: JSON streaming errors include HTTP status codes (moby/moby#54133); the daemon no longer deletes docker0 on restart when it uses a user-managed bridge and default-address-pools (moby/moby#54157); runc in static binaries is updated to v1.5.3 (moby/moby#54183); BuildKit is updated to v0.35.0 (moby/moby#54180); the Go runtime is updated to 1.27.4 (moby/moby#54176, docker/cli#7506).
  • Swarm and overlay networking: engines using the nftables backend can join a Swarm (experimental) (moby/moby#53125); overlay errors after a container gets the IP of a just-removed container on another node are fixed (moby/moby#53833); overlay networking reconverges after a partition when a manager was replaced at a new address (moby/moby#53715); the overlay MTU is no longer 20 bytes too large on an IPv6 Swarm data path (moby/moby#54067); nodes stop exchanging full overlay state with every manager once a minute when healthy (moby/moby#53715); a leaked virtual IP on other networks is fixed (moby/moby#54148).
  • Host networking and firewalls: nftables port publishing is batched per endpoint and address family (moby/moby#54011); the "rule exists" error when publishing several host ports for one container port, with the nftables backend and the userland proxy disabled, is fixed (moby/moby#54031); iptables rules are no longer left behind after a switch to nftables from a release older than 28.0.1 (moby/moby#54129); iptables rules are restored after firewalld stops or starts after the daemon (moby/moby#54012); Swarm tasks reach published ports via their own node's address when ufw drops unsolicited traffic (moby/moby#54006).
  • Network listing and DNS: docker network ls --filter type=builtin --filter type=custom lists all matching networks (moby/moby#54127); DNS resolution on user-defined networks works when the host's /etc/resolv.conf is missing or has no valid nameservers (moby/moby#54140); containers start with networking after an earlier network-error start failure (moby/moby#52480).
  • Rootless: the overlay2 storage driver is allowed in rootless mode when SELinux is enabled (moby/moby#54048); docker cp no longer fails with "remount-ro ... operation not permitted" on read-only bind mounts from nosuid or nodev filesystems (moby/moby#53981).

The full list of pull requests for each component is in the Moby release notes for 29.10.0.

The Sentinel’s Call

Anyone who runs local registries over HTTP or untrusted TLS, and whose daemon.json or daemon flags already set insecure-registries, should update that configuration before upgrading to 29.10.0, because pulls and pushes may fail afterwards. Tooling that reads the Swagger files should plan the move to api/openapi.yaml before the next API version. The experimental jobs extension can wait until a host needs it, and it stays off unless --enable-extension org.mobyproject.jobs.v0 is passed.

Our judgement, drawn only from the facts and sources above.

Sources

  1. Release v29.10.0 · moby/moby · GitHub github.com · Nov 16, 2026
  2. Release api/v1.57.0 · moby/moby · GitHub github.com · Nov 13, 2026
  3. moby/moby#53868: daemon: do not append defaults if insecure-registries are configured github.com · Nov 12, 2026
  4. moby/moby#54093: vendor: github.com/moby/profiles/apparmor & seccomp v0.3.0 github.com · Nov 2, 2026

More on Docker

4 other articles, newest first

Next reading

Edited and approved by Jarosław Krzemiński. Spotted a mistake? Report a correction or read the corrections policy.