Skip to content

docs: clarify proxies map keys in client config.json #25796

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

Open
locker95 wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −0
Open

docs: clarify proxies map keys in client config.json #25796

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
7 changes: 7 additions & 0 deletions content/manuals/engine/cli/proxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`:
Expand Down