Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[docs-scanner] Container proxy table misleadingly presents nested properties as separate parameters

Open Beginner friendly
  • Is something wrong?
#26,263 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@dave123981 is already working on this.

Since Oct 4, 2026.

  • #26268 by @dave123981 — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
docker
Domain
documentation

Research direction

Start with content/manuals/desktop/enterprise/hardened-desktop/settings-management/configure-json-file.md and compare its Container proxy table with settings-reference.md and the nearby nested-setting examples. Update the table so pac and embeddedPac are clearly shown under containersProxy, then verify the rendered documentation matches the example JSON and does not imply separate top-level keys.

Written by the indexing model from the issue text.

Description

File: content/manuals/desktop/enterprise/hardened-desktop/settings-management/configure-json-file.md

Issue

The "Container proxy" section table presents pac and embeddedPac as if they are separate top-level parameters, when they are actually nested properties within the containersProxy object.

From the table:

Parameter OS Description Version
containersProxy Configures the proxy for docker image pull (always enforced) and running container outbound traffic (enforced when transparentPorts is set). For more information see Air-Gapped Containers.
pac Specifies a PAC file URL. For example, "pac": "http://containerproxy/proxy.pac".
embeddedPac Specifies an embedded PAC (Proxy Auto-config) script. For example, "embeddedPac": "function FindProxyForURL(url, host) { return \"PROXY 192.168.92.1:2003\"; }". This setting takes precedence over HTTP, HTTPS, Proxy bypass and PAC server URL.

However, the example JSON in the same file shows the correct structure:

"containersProxy": {
  "locked": true,
  "mode": "manual",
  "http": "",
  "https": "",
  "exclude": [],
  "pac": "",
  "embeddedPac": "",
  "transparentPorts": ""
}

And settings-reference.md correctly documents this as a single JSON object with nested properties.

Why this matters

Administrators reading the table might incorrectly create their JSON configuration with pac and embeddedPac as separate top-level keys instead of nested within containersProxy. This would result in invalid configuration that Docker Desktop would ignore or reject.

Suggested fix

Restructure the table to show the nested relationship, similar to how other nested settings are documented in the same file (e.g., enhancedContainerIsolation.dockerSocketMount.imageList). Alternatively, present containersProxy as a single entry with a JSON example showing all its properties, matching the approach used in settings-reference.md.

Found by nightly documentation quality scanner

Dominant language
Markdown
Stars
4.7k
Forks
8.5k
Avg merge
1d 22h
Merged PRs (30d)
128

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/docs

All issues in docker/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.