Skip to content

4.86-RN #25702

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
aevesdocker wants to merge 1 commit into
base: main
Choose a base branch
from
+41 −0
Draft

4.86-RN #25702

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions content/manuals/desktop/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,47 @@ Docker Desktop versions older than 6 months from the latest release are not avai

For more frequently asked questions, see the [FAQs](/manuals/desktop/troubleshoot-and-support/faqs/releases.md).

## 4.86.0

{{< release-date date="2026-08-10" >}}

{{< desktop-install-v2 all=true win_arm_release="Early Access" version="4.86.0" build_path="/XXXXXX/" >}}

@docker-agent docker-agent Aug 4, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[HIGH] Placeholder build path /XXXXXX/ in desktop-install-v2 shortcode not replaced with real build path

The build_path parameter is set to the placeholder value /XXXXXX/ rather than a real numeric build path. Previous release entries use real paths (e.g., 4.85.0 uses /235549/). This shortcode generates the installer download links shown on the release notes page, so leaving /XXXXXX/ in place will produce broken download links for all users.

Replace /XXXXXX/ with the actual build path before merging.


### Updates

- [Docker Engine v29.7.1](https://docs.docker.com/engine/release-notes/29/#2971)
- [Docker Buildx v0.36.0](https://github.com/docker/buildx/releases/tag/v0.36.0)
- [Docker Scout CLI v1.24.0](https://github.com/docker/scout-cli/releases/tag/v1.24.0)
- [Docker Agent v1.119.0](https://github.com/docker/docker-agent/releases/tag/v1.119.0)

### Bug fixes and enhancements

#### For all platforms

- Gordon now displays specific error messages for tool failures, policy-blocked actions, and loop detection instead of a generic **Agent error**.
- Fixed container stop timeouts and `unless-stopped` restart policies not being honored during engine shutdown.
- Fixed a bug where enabling Docker Offload from the Docker Desktop Dashboard failed when the proxy was configured by the operating system instead of by environment variables.
- Fixed a crash on startup after upgrading, for users whose settings file was written by a very old version.
- Fixed port forwarding for Swarm services that use automatically assigned published ports, including host-mode task ports and repeated ingress port definitions.
- Added a three-mode safety system (Strict, Balanced, Autonomous) to the Gordon AI agent's tool confirmation UI, replacing the previous binary approve/allow-all dialog, with risk-tier labels on confirmation.
- Fixed a flash of incorrect UI content on app launch, such as a brief 'Waiting for the Docker Engine...' screen or unexpected navigation away from gated pages.
- AF_UNIX sockets shared over VirtioFS now work in both directions (host to guest and guest to host).
- Fixed a bug where restarting the VM would steal the window focus.

#### For Mac

- Fixed a bug where a Kubernetes (kind) cluster with Enhanced Container Isolation could fail to recover after a Docker Desktop restart.
- Fixed nftables `fib` expressions failing with "Operation not supported" in `inet` tables on Apple Silicon.

#### For Windows

- Fixed an issue where the Windows installer reported success when it could not write its settings or enterprise policy files.
- Fixed Model Runner failing to start with `CreateJobObject: Access is denied` when Docker Desktop is launched via a Secondary Logon (run-as-user) session.

#### For Linux

- Fixed Docker Desktop failing to start on Linux arm64 hosts due to incorrect QEMU binary path resolution always using the x86_64 binary.

## 4.85.0

{{< release-date date="2026-08-03" >}}
Expand Down