Docker shipped a release on September 8 that moves Gordon — its AI debugging agent — from a dedicated tab to a persistent sidebar, adds Kubernetes cloud cluster management to Docker Offload, patches a container cp destination-escape vulnerability (CVE-2026-17106), and fixes shared-folder bugs that were silently breaking git and pnpm. If you haven’t updated yet, there are reasons to do it today.
Gordon Moves Out of the Tab #
The big UX shift in this release: Gordon is now a persistent right-side drawer rather than a dedicated page. You can open it from anywhere in Docker Desktop without losing your place — which matters more than it sounds.
Previously, asking Gordon for help meant navigating away from the container or image you were looking at. Now the sidebar slides in alongside whatever page you’re on. More useful: containers, images, and volumes with detected issues now display a Gordon indicator. Click it, and Gordon starts a diagnosis immediately — it already knows what you’re looking at and what’s wrong.
This is the same design move VS Code Copilot made when it shifted from a side panel you had to open to inline suggestions that appear where you’re working. The point is that AI assistance shouldn’t require you to go find it. Docker is threading Gordon into the environment rather than leaving it as a feature you have to remember to use.
Gordon’s context-aware suggested questions now surface in the Containers, Images, Volumes, and Builds tabs, pre-loaded based on what’s in a problematic state. The approval model hasn’t changed — Gordon shows you what it wants to do, you approve, it acts. But the path from “something’s broken” to “Gordon is working on it” is now one click instead of several.
Kubernetes Offload Gets Cloud Cluster Control #
Docker Offload — the feature that moves container builds and execution to Docker’s cloud infrastructure without changing your local workflow — now lets you start and stop Kubernetes cloud clusters directly from Docker Desktop, with configurable Kubernetes version and node count.
If your team uses Docker Offload (available since Desktop 4.43), this collapses a common annoyance: you’d set up your Offload environment for builds, then switch to a separate tool to spin up a K8s cluster for testing. Now you can manage the cluster lifecycle from the same place you manage everything else. The feature is especially useful for teams running Docker Desktop in VDI environments, on locked corporate laptops, or for contractors who need a cloud K8s environment without standing up persistent infrastructure. Configure the K8s version, set node count, start the cluster, test, tear it down. No context switching.
Patch This: CVE-2026-17106 #
This release patches CVE-2026-17106, a destination-escape vulnerability in docker container cp. A malicious container could exploit the copy process to write files outside the intended destination on the host — including shell configuration, SSH keys, executables, and persistence mechanisms. Docker Sandboxes were also affected via sbx cp. The Imperva Red Team research (CopyEscape) documented the full attack path.
The fix is in this release. If you haven’t updated: update.
Bug Fixes Worth Knowing About #
A few of the less glamorous fixes have real workflow impact:
mmap()of a file on a Synchronized File Share was failing with “No such device,” which brokegitandpnpm— the kind of intermittent failure that makes you blame your code before you blame Docker.renameat2(RENAME_EXCHANGE)on a shared folder was overwriting the target instead of atomically swapping files — a subtle bug that corrupts operations expecting atomic rename behavior.- Repeatedly replacing files on a shared folder was leaking VM disk space until Docker Desktop was restarted.
- Bind-mount roots were intermittently reporting ownership as 0:0, triggering git’s “detected dubious ownership” false positives on Windows.
The Dashboard also now shows the specific reason Docker Engine failed to start when available, replacing the previous opaque dead end. It’s a small change that saves a lot of digging.
How to Get It #
Docker Desktop ships updates roughly every two weeks. Check for updates via the Docker Desktop menu → “Check for updates,” or review the full Docker Desktop release notes. The Gordon sidebar and CVE-2026-17106 patch are both in this release, so there’s no reason to wait.
Full Gordon documentation — including how to configure it with a working directory for project context — is at docs.docker.com/ai/gordon. Docker Offload configuration, including the new Kubernetes cluster options, is at docs.docker.com/offload/configuration.
Docker has been steadily embedding Gordon deeper into the workflow since its GA in May. Moving from a chat destination to an ambient assistant is the right direction. The next logical step is proactive alerts — Gordon surfacing issues before you notice them. This release is a step along that path.