Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Ping2Prompt story card: Docker Engine 29.10.0: check insecure-registries before you upgrade. Release, Docker.

    Docker Engine 29.10.0 changes how loopback registries are treated as insecure

    Automated source check

    Docker

    Update (2026-11-16): This article now covers everything published about this release (2 sources), merged from separate reports.

    What changed

    Docker Engine 29.10.0 is out, with a potential breaking change for local registries. If insecure-registries is set in daemon.json, or you pass --insecure-registry, loopback addresses (127.0.0.0/8 and ::1/128) are no longer treated as insecure automatically. Pulls and pushes to a local registry over HTTP or with an untrusted TLS certificate may then fail.

    The Engine API spec now uses OpenAPI 3.2 as its source format. A generated Swagger 2.0 spec is still published, but future API versions get no per-version Swagger 2.0 copy. New and experimental: jobs, which are one-shot or cron-scheduled workloads, enabled with --enable-extension org.mobyproject.jobs.v0.

    Obsolete socket families are now blocked in the default AppArmor and seccomp profiles. Packages are now available for AlmaLinux, Oracle Linux and Rocky Linux. Fixes cover networking, such as iptables restoration after firewalld restarts, and the docker0 interface being deleted on restart with a user-managed bridge.

    Who needs to act

    If you set insecure-registries and use a local registry on loopback, check it before upgrading. Either configure TLS with a trusted certificate, or list only the addresses you need, such as localhost:5000. If you omit insecure-registries, loopback registries stay insecure by default.

    If you rely on the API's Swagger 2.0 files, plan a move to the OpenAPI 3.2 specs. Everyone else can take this release on a normal schedule. The commands and settings here come from the release notes listed under Sources; check them against your own setup before running them.

    What the sources don't cover

    The release notes text is truncated, so some networking and other changes are not covered here. No release date is given.

    Sources


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion