What moby/moby shipped
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
Week of November 9, 2026
What shipped
- Release candidate v29.10.0-rc.2 was published, flagged as a potential breaking change for users who explicitly configure local insecure registries. Release
- Client v0.6.3 was released with fixes for progress stream error classification, request cancellation and deadlines during TLS setup, and the OpenTelemetry span of hijacked requests. Release
- API v1.57.0 was released, moving the Engine API specification source to OpenAPI 3.2 while still publishing a generated Swagger 2.0 file. Release
- The daemon no longer appends default insecure registries when they are explicitly configured, aligning localhost registry handling with Docker's configuration. Pull request #53868
- Image inspect and list with the containerd image store now return results when the host platform variant of a multi-platform image was never pulled. Pull request #54040
- The project was updated to Go 1.27.4, which includes 12 security fixes. Pull request #54176
- The runc binary was updated to v1.5.3, which fixes a high-severity vulnerability affecting checkpoint and restore of containers. Pull request #54183
- The crun binary was updated to v1.31, which refuses CRIU external mount keys that CRIU cannot read back. Pull request #54184
- BuildKit was vendored at v0.35.0. Pull request #54180
- Lazy mount detach in the snapshotter is now Linux-only, fixing builds on macOS and FreeBSD. Pull request #53780
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
- Release v29.10.0-rc.2, with a potential breaking change for explicit insecure registry configuration. Release
- Release client v0.6.3 with progress stream error classification and TLS setup fixes. Release
- Release API v1.57.0; the specification source is now OpenAPI 3.2. Release
- Do not append default insecure registries when they are configured. Pull request #53868
- Fix image inspect and list with the containerd image store when the host platform was not pulled. Pull request #54040
- Update to Go 1.27.4. Pull request #54176
- Update runc to v1.5.3. Pull request #54183
- Update crun to v1.31. Pull request #54184
- Update BuildKit to v0.35.0. Pull request #54180
- Only lazily detach mounts on Linux. Pull request #53780
- Skip the time namespace for plugins on kernels without support. Pull request #54155
- Do not remove docker0 when the default bridge is user-managed. Pull request #54157
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
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
- Docker Engine 29.9.3 was released with fixes for multiple security vulnerabilities affecting Docker Engine and related components. Release
- The vendored swarmkit dependency was updated to v2.1.3 to fix a vulnerability where an attacker with a valid worker-node TLS certificate and private key could obtain a manager-node certificate shortly after joining. Pull request #54114
- BuildKit was updated to v0.34.2, fixing a case where a build that resolved metadata for the same Git source reference twice could reuse the wrong data. Pull request #54106
- The vendored YAML v2 library was updated to v2.4.5 to fix a validation bypass where quoted null and tilde scalars skip UnmarshalYAML validation. Pull request #54109
- The daemon now refuses the containerd migration when userns-remap is enabled, matching the existing refusal to start with the containerd snapshotter explicitly enabled. Pull request #54139
- The embedded containerd in the daemon now loads configuration drop-ins from containerd.d/*.toml next to the daemon configuration file, while root, state and gRPC address stay under dockerd control. Pull request #53946
- Swarm service load balancing gained a native nftables implementation with feature parity to the iptables firewall mode, covering both NAT and DSR modes. Pull request #53125
- The nftables firewall backend now removes the per-bridge ACCEPT and ICC rules left in filter-FORWARD by releases older than 28.0.1 that ran with iptables, including on internal networks. Pull request #54129
- A regression in network listing was fixed so a request filtering on more than one type value, such as builtin and another type, matches every value instead of only one. Pull request #54127
- The internal resolver now falls back to default nameservers when the host has no valid external nameservers or /etc/resolv.conf is missing, instead of leaving the embedded DNS resolver without upstream servers. Pull request #54140
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
- Release 29.9.3 with fixes for multiple security vulnerabilities affecting Docker Engine and related components. Release
- Vendor github.com/moby/swarmkit/v2 v2.1.3, fixing CVE-2026-115539. Pull request #54114
- Update BuildKit to v0.34.2. Pull request #54106
- Vendor go.yaml.in/yaml/v2 v2.4.5 to fix a YAML unmarshaler validation bypass. Pull request #54109
- Refuse containerd migration when userns-remap is enabled. Pull request #54139
- Load containerd.d/*.toml configuration drop-ins for the embedded containerd. Pull request #53946
- Add an nftables implementation of Swarm service load balancing with NAT and DSR support. Pull request #53125
- Fix cleanup of iptables rules left by releases older than 28.0.1 when starting with the nftables backend. Pull request #54129
- Fix network listing to match every value of the type filter. Pull request #54127
- Fall back to default nameservers in the internal resolver when the host has no valid external nameservers. Pull request #54140
- Map ErrFailedPrecondition to 412 and ErrResourceExhausted to 429 in HTTP status handling. Pull request #54125
- Add experimental support for one-shot and scheduled workloads as a builtin daemon extension. Pull request #53485
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.
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
- Built-in extensions can now be enabled, disabled, and configured through daemon.json. Pull request #54059
- Die events now carry a restarting attribute so consumers can tell a container is about to restart without inspecting it. Pull request #50908
- Rootless dockerd can use overlay2 when SELinux is enabled on the host. Pull request #54048
- The overlay driver now accounts for the larger IPv6 VXLAN outer header when computing MTU. Pull request #54067
- Publishing multiple host ports for the same container port with the nftables backend and the userland proxy disabled no longer fails with a rule exists error. Pull request #54031
- Bridge port publishing now batches firewall updates, applying one nftables transaction per address family. Pull request #54011
- The daemon now restores its iptables rules when firewalld stops and deletes them. Pull request #54012
- NetworkDB bootstrap rejoin was fixed for clusters that have split. Pull request #53715
- Client tracing spans for attach and exec connections now end after a successful hijack. Pull request #54052
- Windows binary exports now include containerd and its runtime shim. Pull request #54069
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
- Daemon: allow built-in extensions to be enabled, disabled and configured in daemon.json. Pull request #54059
- Api: add a restarting attribute to die events. Pull request #50908
- Overlay2: allow rootless mode with SELinux enabled. Pull request #54048
- Overlay: account for IPv6 VXLAN overhead when computing MTU. Pull request #54067
- Nftabler: allow duplicate hairpin masquerade rules for multiple published host ports. Pull request #54031
- Bridge: batch firewall updates for published ports. Pull request #54011
- Libnetwork: restore iptables rules when firewalld stops. Pull request #54012
- Networkdb: fix periodic bootstrap rejoin for split clusters. Pull request #53715
- Client: end the otelhttp span after a successful hijack. Pull request #54052
- Dockerfile: include containerd and its runtime shim in Windows binary exports. Pull request #54069
- Api/types/network: deep-copy endpoint MAC addresses. Pull request #54074
- Vendor: update github.com/klauspost/compress to v1.20.2. Pull request #54054
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.
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
- Released v29.9.2, which includes a Go runtime update that addresses CVE-2026-111943 by rejecting certificate chains containing eight revoked eMudhra intermediates. Release
- The daemon now selects the maximum arm64 variant supported by the current CPU when an image has several ARM64 variants, detected using ARM64 ELF hwcaps. Pull request #53910
- Updated hcsshim to v0.15.0 to fix Windows layer exports containing NTFS sparse files. Pull request #53745
- Fixed docker cp with read-only socket mounts in rootless mode by keeping the nosuid, nodev, noexec and atime flags the kernel locks in a user namespace. Pull request #53981
- The daemon now fills in the http request route pattern, which is used for traces and metrics to reduce cardinality on paths with variable segments. Pull request #54001
- Updated the build to Go 1.26.10, which includes a crypto/x509 security fix. Pull request #53988
- Backported the Go 1.26.10 update to the 29.x branch. Pull request #53989
- Adjusted build tags to reduce binary sizes, including disabling unused gRPC tracing in dockerd for a reduction of approximately 232 KiB. Pull request #53992
- Vendored buildkit v0.34.1, a binary-only release with no code changes in vendor. Pull request #53995
- Replaced the rapid-based property test for plugin capability IDs with a table-driven test and Go's built-in fuzzing support. Pull request #53980
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
- Release v29.9.2, including a Go runtime update addressing CVE-2026-111943. Release
- Select the maximum arm64 variant supported by the CPU using ARM64 ELF hwcaps. Pull request #53910
- Vendor hcsshim v0.15.0 to fix Windows sparse-file exports. Pull request #53745
- Fix docker cp with read-only socket mounts in rootless mode. Pull request #53981
- Fill in the http request route pattern in the daemon server. Pull request #54001
- Update to Go 1.26.10. Pull request #53988
- Backport the Go 1.26.10 update to the 29.x branch. Pull request #53989
- Adjust build tags to reduce binary sizes, including disabling unused gRPC tracing in dockerd. Pull request #53992
- Vendor buildkit v0.34.1. Pull request #53995
- Replace rapid with standard Go fuzzing in api/types/plugin tests. Pull request #53980
- Update golangci-lint to v2.14.0 in the Dockerfile. Pull request #53114
- Update github.com/godbus/dbus/v5 to v5.2.4. Pull request #53969
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.
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
- Release v29.9.1 shipped, including the containerd update to v2.4.2 with fixes for listed security vulnerabilities. Release
- The Dockerfile now uses containerd v2.4.2, bringing the same security updates. Pull request #53936
- The vendored github.com/containerd/containerd/v2 dependency moved to v2.4.2 with security fixes. Pull request #53935
- Docker save no longer leaks a layer reference for every repeated diff ID in an image on the graph-driver image store. Pull request #53927
- Container list with size=true no longer fails entirely when the size lookup for one container fails. Pull request #53921
- A data race on the removal error after a container removal was fixed by setting the error while holding the state lock. Pull request #53950
- The client TLS dial path now honors context cancellation, so a stalled TLS handshake no longer blocks DialHijack past its context expiry. Pull request #53903
- The bridge driver leaves bridges that firewalld has bound to another zone alone instead of failing network setup. Pull request #53907
- Swarm ingress sandbox endpoints on
docker_gwbridgeno longer get IPv6 addresses. Pull request #53940 - Image digest resolution in the cluster code now works with registry mirrors. Pull request #53933
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
- Release v29.9.1, including containerd v2.4.2 with security fixes. Release
- Dockerfile: update to containerd v2.4.2. Pull request #53936
- Vendor: github.com/containerd/containerd/v2 v2.4.2. Pull request #53935
- Image/tarexport: release the layer when its diff was already saved. Pull request #53927
- Don't fail container list when size lookup fails. Pull request #53921
- Daemon/container: fix a data race on the error after a container removal. Pull request #53950
- Client: honor context cancellation when dialing TLS. Pull request #53903
- Libnetwork: leave bridges in other firewalld zones. Pull request #53907
- Libnetwork: no IPv6 for ingress sandbox on
docker_gwbridge. Pull request #53940 - Daemon/cluster: fix image digest resolution with registry mirrors. Pull request #53933
- Daemon: reject non-link-local addresses passed as link-local IPs. Pull request #53923
- Propagate plugin privilege fetch errors. Pull request #53934
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.
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
- Docker Engine was updated to Go 1.26.9, which includes 15 security fixes. Pull request #53893
- The client now honors context cancellation during hijack handshakes instead of blocking indefinitely once connected. Pull request #53889
- Lazy pulls stay lazy for remote snapshotters such as stargz, which previously fetched every layer blob. Pull request #53877
- The release branch was updated to 29.9.1. Pull request #53902
- A race in pull progress layer suppression was fixed by no longer sharing hideLayers between the pull handler and progress state. Pull request #53856
- Pull progress for existing content was corrected so progress is accurate when all content already exists. Pull request #53857
- A lightweight merge queue was added that runs golangci-lint to catch compile errors before merging. Pull request #53885
- An integer overflow in boltdb metadata allocation was prevented by checking the value length before computing buffer capacity. Pull request #53884
- Libnetwork now writes resolver files only when sandbox paths are explicitly requested. Pull request #53848
- Libnetwork no longer runs a resolver in load-balancer sandboxes. Pull request #53846
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
- Update to Go 1.26.9, including 15 security fixes. Pull request #53893
- Client: honor cancellation during hijack handshakes. Pull request #53889
- Daemon/containerd: keep lazy pulls lazy for remote snapshotters. Pull request #53877
- Daemon/containerd: fix race in pull progress layer suppression. Pull request #53856
- Daemon/containerd: fix pull progress for existing content. Pull request #53857
- Libnetwork: write resolver files only when asked. Pull request #53848
- Libnetwork: don't run a resolver in load-balancer sandboxes. Pull request #53846
- Libnetwork/kvstore/boltdb: prevent integer overflow in allocation. Pull request #53884
- Ci: add a lightweight merge queue that runs golangci-lint. Pull request #53885
- Integration/build: check build errors in the build response stream. Pull request #53880
- Libcontainerd: handle native event-stream cancellation errors. Pull request #53865
- Builder: COPY --from no longer remaps already remapped IDs. Pull request #53859
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
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
- Released v29.9.0-rc1 with fixes for containerd image store pulls skipping required layer blobs when unpacked layers already exist. Release
- Released v29.8.2 with security fixes including CVE-2026-53493 for crafted OCI image pulls. Release
- Released v25.0.18 with fix for CVE-2026-17106 where crafted tar archives could write outside the extraction directory. Release
- Fixed daemon to release RootlessKit API connections after each /version call, preventing connection leaks. Pull request #53836
- Fixed overlay network driver to not remove in-use IPsec tunnels when encrypted overlay endpoints are still active. Pull request #53420
- Fixed bridge network driver so published ports are reachable even when inter-container communication is disabled. Pull request #53723
- Fixed DOCKER-INGRESS chain cleanup for bridge networks to properly handle upgrades from daemons older than 28.0.1. Pull request #53825
- Updated BuildKit to v0.34.0-rc1. Pull request #53830
- Released client/v0.6.1 with WithHTTPRequestHook option, deprecated WithResponseHook, and fixed response hooks for hijacked connections. Release
- Split containerd image loading into separate import and unpack steps for better control of the loading process. Pull request #53596
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
- 29.8.2: Security fixes for CVE-2026-53493 Release
- 25.0.18: Security fix for CVE-2026-17106 Release
- 29.9.0-rc.1: containerd image store fixes for layer blob handling Release
- Daemon: Release RootlessKit API connection after /version calls Pull request #53836
- Libnetwork/overlay: Don't remove in-use IPsec tunnels Pull request #53420
- Libnetwork/bridge: Reach published ports with icc=false Pull request #53723
- Libnetwork/bridge: Fix DOCKER-INGRESS cleanup on upgrades Pull request #53825
- Client/v0.6.1: Add WithHTTPRequestHook, fix hijacked response hooks Release
- Vendor: Update BuildKit to v0.34.0-rc1 Pull request #53830
- Daemon/containerd: Split image loading into import and unpack steps Pull request #53596
- Client: Fix response hooks for hijacked HTTP connections Pull request #53821
- Daemon: Preserve prefixes on config reload to fix default address pools Pull request #53753
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.
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
- Fixed host-gateway options restoration during daemon live restore, which was causing restored containers using host-gateway extra-host mappings to lose their sandbox configuration. Pull request #53093
- Added integration tests for Swarm published ports over IPv6 to verify correct handling of IPv6 traffic on service ports. Pull request #53727
- Backported fix for docker cp failures with nested bind mounts where one bind mount covers a directory and another covers a path inside it. Pull request #53725
- Fixed incorrect em dash character in the --force hint message when deleting platform-specific image variants. Pull request #53768
- Improved error message for one-character container names to directly report the minimum-length requirement instead of blaming the character set. Pull request #53484
- Fixed Makefile to respect BIND_DIR environment variable instead of overriding it, making environment configuration consistent with other variables. Pull request #53776
- Improved OpenAPI compatibility by documenting that image operation query parameters use repeated keys instead of implicit CSV encoding. Pull request #53626
- Fixed ImageManifestSummary.ImageData swagger definition by removing invalid required field reference to UnpackedSize. Pull request #53750
- Optimized Swarm test performance by configuring container tasks with init processes to properly handle SIGTERM signals. Pull request #53743
- Enabled integration network and networking tests in VM CI workflows to improve test coverage. Pull request #53710
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
- Daemon: Restore host-gateway options after networks load to fix live restore of containers using host-gateway extra-host mappings Pull request #53093
- Integration: Add tests for Swarm published ports over IPv6 Pull request #53727
- Daemon: Fix docker cp with nested bind mounts (backport to 25.0) Pull request #53725
- Daemon/containerd: Fix em dash character in --force hint for platform-specific image deletion Pull request #53768
- Daemon: Clarify error message for short container names to directly report minimum-length requirement Pull request #53484
- Makefile: Honour BIND_DIR from the environment Pull request #53776
- Api/swagger: Document repeated query keys for image operation parameters instead of CSV encoding Pull request #53626
- Api/swagger: Fix invalid required field in ImageManifestSummary.ImageData Pull request #53750
- Integration: Speed up Swarm tests by using init processes for proper signal handling Pull request #53743
- Client: Update github.com/docker/go-connections to v0.8.1 Pull request #53708
- Ci: Allow overriding BuildKit repository and version for temporary testing Pull request #53774
- CI: Enable integration network and networking tests in VM workflows Pull request #53710
This week: host-gateway restore fix, Swarm IPv6 port tests, nested bind mount docker cp fix, improved error messages, and test infrastructure improvements.
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.