From 56c9c20763afc2373187cfbc02c26badcbc2882a Mon Sep 17 00:00:00 2001
From: Dean Chen <51218137+locker95@users.noreply.github.com>
Date: Wed, 12 Aug 2026 01:27:34 +0500
Subject: [PATCH] docs: clarify proxies map keys in client config.json

Call out that keys must be default or the real daemon endpoint from
context ls, not a placeholder host like docker.example.com.

Related to docker/cli#7046

Signed-off-by: Dean Chen <862469039@qq.com>
---
 content/manuals/engine/cli/proxy.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/content/manuals/engine/cli/proxy.md b/content/manuals/engine/cli/proxy.md
index 050c4160ec00..3e1e31cfb4c8 100644
--- a/content/manuals/engine/cli/proxy.md
+++ b/content/manuals/engine/cli/proxy.md
@@ -139,6 +139,13 @@ settings for all daemons that the client connects to.
 To configure the proxies for individual daemons,
 use the address of the daemon instead of the `default` key.
 
+The map key must be exactly `default`, or the daemon endpoint string the CLI
+uses for that context (the **DOCKER ENDPOINT** column from `docker context ls`,
+for example `unix:///var/run/docker.sock`, `ssh://user@host`, or
+`tcp://host:2376`). A placeholder such as `http://docker.example.com` is not a
+magic value — if that string is not the active endpoint, the CLI ignores it and
+falls back to `default` only when the `default` entry exists.
+
 The following example configures both a default proxy config,
 and a no-proxy override for the Docker daemon on address
 `tcp://docker-daemon1.example.com`: