Shipped · DevOps and infrastructure

What moby/moby shipped

The public repository of Moby · github.com/moby/moby

Written by FoxPlug from the repository's own releases; not affiliated with Moby. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/moby/moby; Moby did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

See the update FoxPlug writes for moby, free

Week of November 9, 2026

What shipped

Why it matters

This week's releases touch both the client and the Engine API: client v0.6.3 tightens error handling and TLS connection behavior, and API v1.57.0 changes the source format of the specification to OpenAPI 3.2 while keeping Swagger 2.0 output for existing tooling. A release candidate also lands with a possible breaking change for users who explicitly set insecure registries, so daemon configuration around local registries is worth checking. Alongside that, dependency and toolchain updates bring security fixes in Go, runc and crun.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Moby this week: client v0.6.3 and API v1.57.0 released, plus v29.10.0-rc.2 flagged for a possible breaking change to explicit insecure registry config. Go, runc and crun updates bring security fixes. Containerd image store fix for inspect and list when the host platform was never

Post for LinkedIn

This week in Moby: client v0.6.3 shipped with better error classification for progress streams and TLS connection fixes, and API v1.57.0 moved the Engine API specification source to OpenAPI 3.2 while still publishing a Swagger 2.0 file for existing tooling. Release candidate v29.10.0-rc.2 is out and is flagged as a potential breaking change for setups that explicitly configure insecure registries. We also moved to Go 1.27.4 with 12 security fixes, updated runc to v1.5.3 for a high-severity checkpoint/restore vulnerability, updated crun to v1.31, and vendored BuildKit v0.35.0. On the daemon side, inspect and list now work with the containerd image store when an image's host platform variant was never pulled.

Week of November 2, 2026

What shipped

Why it matters

This week brought security fixes to both release lines, including the Engine 29.9.3 release and updated vendored libraries for Swarm and BuildKit, so users on current versions should plan upgrades. It also moved networking forward: native nftables load balancing for Swarm services, cleaner firewall handling for networks restored from older releases, and an internal DNS resolver that no longer goes without upstream servers on misconfigured hosts.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Security fixes this week: Engine 29.9.3, swarmkit v2.1.3 and BuildKit v0.34.2. Also new: native nftables load balancing for Swarm services and internal DNS that falls back to default nameservers.

Post for LinkedIn

This week in Moby: Docker Engine 29.9.3 shipped with fixes for multiple security vulnerabilities, along with an update to swarmkit v2.1.3 for a worker-to-manager certificate issue and BuildKit v0.34.2 for a Git source metadata bug. Swarm service load balancing now has a native nftables implementation matching the iptables mode, and the embedded containerd accepts configuration drop-ins. The nftables backend also cleans up firewall rules left by older iptables-based releases, and the embedded DNS resolver now falls back to default nameservers when the host has none. Network listing with multiple type filters was fixed.

Week of October 26, 2026

What shipped

Why it matters

This week's changes touch daemon configuration, networking and container event consumers. Extensions become configurable from daemon.json, rootless overlay2 works with SELinux, and overlay MTU and nftables port publishing are corrected. Die events gain a restarting attribute that tools such as Compose can use without inspecting the container.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: extensions configurable via daemon.json, die events gain a restarting attribute, rootless overlay2 works with SELinux, overlay MTU accounts for IPv6 VXLAN, and nftables port publishing fixes.

Post for LinkedIn

This week in Moby: built-in extensions can be enabled, disabled and configured through daemon.json. Die events now include a restarting attribute so tools like Compose can detect a restarting container without inspecting it. Rootless dockerd can use overlay2 with SELinux enabled, the overlay driver accounts for IPv6 VXLAN overhead in MTU, and nftables port publishing no longer fails when multiple host ports map to the same container port. The daemon also restores iptables rules when firewalld stops, and Windows binary exports now include containerd and its runtime shim.

Week of October 19, 2026

What shipped

Why it matters

This week brings a security release in v29.9.2 that rejects certificate chains with revoked intermediates, along with Go 1.26.10 updates and their 29.x backport. It also fixes Windows sparse-file layer exports and docker cp with read-only socket mounts in rootless mode, both of which affect everyday container workflows. Smaller changes improve arm64 image selection and request tracing and metrics.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Moby v29.9.2 is out with a Go runtime update addressing CVE-2026-111943. Also this week: arm64 variant selection by CPU hwcaps, a fix for Windows sparse-file layer exports, and a rootless docker cp fix for read-only socket mounts.

Post for LinkedIn

This week Moby released v29.9.2, which includes a Go runtime update addressing CVE-2026-111943 by rejecting certificate chains that include eight revoked eMudhra intermediates. On arm64, the daemon now pulls the maximum image variant supported by the current CPU, using ARM64 ELF hwcaps instead of an external library. Windows layer exports containing NTFS sparse files are fixed by updating hcsshim to v0.15.0, and docker cp now works with read-only socket mounts in rootless mode. The daemon also fills in the HTTP request route pattern to reduce trace and metric cardinality, and the build moved to Go 1.26.10, backported to the 29.x branch.

Week of October 12, 2026

What shipped

Why it matters

This week brought a security release with an updated containerd, plus fixes for resource leaks, cancellation and race conditions in container and client paths. Several changes address cases where one bad container or a stalled handshake could degrade the rest of the workflow, and network and swarm setup got corrections for firewalld zones and ingress IPv6.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Moby this week: v29.9.1 released with containerd v2.4.2 and security fixes. Also landed: a docker save layer leak fix, container list surviving size lookup failures, TLS dial cancellation, and swarm ingress IPv6 corrections.

Post for LinkedIn

This week in Moby: v29.9.1 shipped, including the containerd v2.4.2 update with fixes for listed security vulnerabilities. The Dockerfile and vendored containerd dependency were updated to match. Other changes: docker save no longer leaks a layer reference for repeated diff IDs; container list no longer fails when a size lookup fails for one container; a data race on the container removal error was fixed; the client TLS dial path now honors context cancellation; bridge networks bound to other firewalld zones are left alone; swarm ingress sandbox endpoints on docker_gwbridge no longer get IPv6 addresses; and image digest resolution now works with registry mirrors.

Week of October 5, 2026

What shipped

Why it matters

This week's changes tighten correctness in areas that directly affect day-to-day container runs: pull behaviour with lazy snapshotters, network resolver file handling in load-balancer sandboxes, and client cancellation during hijack handshakes. Security and build hygiene also moved forward with a Go runtime update carrying 15 security fixes, a lighter merge queue running golangci-lint, and a boltdb allocation overflow fix. Together they reduce unexpected stalls, redundant pulls and silently failing merges for people building and running containers.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: Engine updated to Go 1.26.9 with 15 security fixes. Client honors cancellation during hijack handshakes. Lazy pulls stay lazy with remote snapshotters. libnetwork writes resolver files only when asked and stops running a resolver in load-balancer sandboxes. A lightweig

Post for LinkedIn

Changes of note this week in Moby. The Engine was updated to Go 1.26.9, which carries 15 security fixes. The client now honors context cancellation during hijack handshakes, so an upgrade request can no longer block indefinitely after connecting. Pulls with remote snapshotters such as stargz now keep lazily prepared layers lazy instead of fetching every layer blob, and pull progress for already-present content was corrected, along with a race in progress layer suppression. In networking, libnetwork writes resolver files only when sandbox paths are requested and no longer runs a resolver in load-balancer sandboxes. An integer overflow in boltdb metadata allocation was prevented. A lightweight merge queue that runs golangci-lint was added, and integration build tests now check build errors r

Week of September 28, 2026

What shipped

Why it matters

This week includes critical security releases (v29.8.2 and v25.0.18) addressing CVEs in OCI image handling and tar extraction, plus important fixes for rootless mode, network overlay tunnels, and bridge network connectivity. The v29.9.0-rc1 addresses image layer handling issues in containerd integration.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Moby 29.8.2 and 25.0.18 ship with security fixes for CVE-2026-53493 and CVE-2026-17106. v29.9.0-rc1 improves containerd image layer handling. Network and rootless improvements also included.

Post for LinkedIn

New releases from Moby this week: v29.8.2 and v25.0.18 address security vulnerabilities (CVE-2026-53493, CVE-2026-17106). v29.9.0-rc1 fixes containerd image store layer handling. Additional improvements include rootless mode connection handling, overlay network tunnel management, and bridge network port reachability when inter-container communication is disabled.

Week of September 21, 2026

What shipped

Why it matters

This week includes important fixes for container restore, Swarm networking, bind mounts, and error messages that developers will encounter in production scenarios. The improvements to test infrastructure and OpenAPI compatibility help ensure more reliable deployments and better client code generation. Several dependency updates and CI improvements strengthen the project's foundation.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

This week: host-gateway restore fix, Swarm IPv6 port tests, nested bind mount docker cp fix, improved error messages, and test infrastructure improvements.

Post for LinkedIn

Moby's latest updates focus on reliability and correctness. We fixed daemon live restore for containers using host-gateway mappings, added IPv6 testing for Swarm published ports, resolved docker cp issues with nested bind mounts, and clarified error messages. Infrastructure improvements include better test coverage and OpenAPI specification compliance for improved client generation.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-11-16.

Is this your repo? Ask us to remove this page.

Leaderboard