docs: document upstream proxy chaining for sandboxes#25359
Merged
Conversation
Explain how sandbox outbound traffic chains to an upstream proxy, the HTTP_PROXY/HTTPS_PROXY/NO_PROXY variables the daemon reads, the DOCKER_SANDBOXES_PROXY override scoped to sandbox traffic, and the HTTP-only and proxy.pac limitations. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Rob Murray <rob.murray@docker.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The new Upstream proxy subsection is clear, well-scoped, and accurately documents sandbox proxy chaining behavior. One minor style guide issue was found.
| Severity | Count |
|---|---|
| 🟡 Medium | 1 |
Restructure the two limitation bullets to drop parenthetical asides, per STYLE.md guidance to avoid parentheses in technical documentation. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Rob Murray <rob.murray@docker.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Documents how Docker Sandboxes' outbound traffic interacts with an upstream (for example, corporate) proxy. This was previously only described in internal-facing notes.
Adds an Upstream proxy subsection under the existing Networking heading on the Sandboxes architecture page, covering:
HTTP_PROXY,HTTPS_PROXY, andNO_PROXYenvironment variables the sandbox daemon reads (including lowercase equivalents), and usingNO_PROXYfor direct-reach exclusions.DOCKER_SANDBOXES_PROXY— scoped to sandbox traffic only, sets one URL for both HTTP and HTTPS, and doesn't affect image pulls or the daemon's own requests.proxy.pacfiles aren't supported.Prompted by support questions about routing sandbox traffic through a corporate proxy.
🤖 Generated with Claude Code