---
title: "Docker Sandboxes Network and Credentials: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/docker-sandboxes-network-credentials/
description: "Configure standalone sbx egress policy and service credentials while distinguishing proxy sentinels, OAuth passthrough and host-side secret resolution."
---

# Docker Sandboxes Network and Credentials: review, setup & limitations · Undominated.ai

> Configure standalone sbx egress policy and service credentials while distinguishing proxy sentinels, OAuth passthrough and host-side secret resolution.

[← Explore all skills](/skills/)

SANDBOX SECURITY / docker

# Docker Sandboxes Network and Credentials

Configure standalone sbx egress policy and service credentials while distinguishing proxy sentinels, OAuth passthrough and host-side secret resolution.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/docker/skills/tree/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 4 linked sources
 Publisher docker
 Licence [Apache-2.0 ↗](https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/LICENSE)
 Revision f79172733725
 [Read what was—and wasn’t—checked ↓](#review)

“Use this skill when configuring what a Docker Sandboxes (`sbx`) sandbox can reach on the network or which credentials it authenticates with, even if the user just says they want to "let the agent call an internal API", "block all network access", "give the agent a GitHub token", or "use a private registry image for a sandbox". Covers `sbx policy init/allow/deny/ls/inspect/log/check/rm network` (global and per-sandbox egress rules, deny-over-allow precedence) and `sbx secret set/set-custom/ls/rm/import` (service secrets, dynamic secrets via --ref/--command, and registry pull credentials with their host-pulls-only-by-default injection scope).”

 [docker · upstream description ↗](https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - It separates Docker Sandboxes egress policy from credential injection, and storing a secret does not open the network.
- Registry credentials stay on the host by default and are not injected into the sandbox filesystem.
- Separates global/per-sandbox policy and credentials, with deny precedence and targeted diagnostics.
- Explains why storing a credential does not grant egress and why OAuth passthrough can expose real tokens.

### A good fit for

 - Deciding what an sbx sandbox may reach, separately from which credential the proxy may use
- Avoiding a plain --env or --kit-arg that would put a secret in shell history
- Allow one sandbox to call a private API without broad global egress.
- Debug a registry pull or service authentication failure with policy checks and scoped secret inspection.

### Weigh up before choosing

 - Egress policy does not protect a credential that has already left the sandbox.
- sbx policy reset deletes the entire local policy and is not a first troubleshooting step.
- OAuth passthrough is not a guarantee that the agent cannot read a token.
- This review did not execute the resource.
- Targets standalone sbx, not legacy docker sandbox or Docker Agent allowlists.
- Network restrictions do not protect a real credential after it leaks; dynamic secret commands execute with host privileges.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - skills/docker-sandboxes-network-credentials/SKILL.md
- README.md
- LICENSE

### Our findings

 - Network policy and service secrets are different controls: storing a secret does not grant network access.
- A local deny can narrow egress; the source says it cannot turn an organization-level allow into a broader grant. Matching deny rules take precedence over allow rules for the same hostname or CIDR.
- Registry credentials authenticate host pulls and are never injected into the sandbox by default.
- The skill does not treat egress policy as protection after a credential has leaked.
- Definition explicitly documents reset as deleting local policy and stopping running sandboxes.
- Credential injection and network access are independent; registry host-pull scope differs from in-sandbox injection.

### Not established by this review

 - The resource was not executed and its tools were not called.
- No skill execution, authenticated service operation, or outcome benchmark was performed.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/README.md)

DOCUMENTED COMMAND

 npx skills add docker/skills/skills/docker-sandboxes-network-credentials Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/docker/skills/tree/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials Copy reviewed-revision command ↗ - Install the pinned skill directory interactively, retaining its bundled references and scripts.
- Identify the standalone CLI and target sandbox, then inspect policy before changing rules.
- Use interactive secret storage and verify the intended domain/scope; avoid policy reset for routine diagnostics.

### Before you start

 - Standalone sbx CLI matching supported commands
- Host credentials for selected services or registry

### Compatibility

Agents supporting directory-based SKILL.md instructions

### Local instructions; runtime access depends on the workflow

 - Changes egress rules and host credential storage; global defaults affect multiple sandboxes.
- Dynamic --command/--ref resolution runs on the host; OAuth passthrough can deliver real tokens into the sandbox.

### Cost model

The skill is free; service usage and infrastructure can incur charges.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned skill definition ↗](https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials/SKILL.md) Checked 2026-10-14 https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials/SKILL.md Supports: summary, whySelected, bestFor, limitations, install, access, review
- [Publisher repository and installation guidance ↗](https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/README.md) Checked 2026-10-14 https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/README.md Supports: install
- [Apache-2.0 licence ↗](https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/LICENSE) Checked 2026-10-14 https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/LICENSE Supports: license
- [2026-10-15 C2-W30 source re-review at the existing pin ↗](https://raw.githubusercontent.com/docker/skills/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/docker/skills/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials/SKILL.md Supports: upstreamDescription, review.notTested, review.reviewedAt, review.findings

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Docker Agent Configuration ↗ Build Docker Agent configurations with per-agent toolsets, provider credentials, delegated teams and bounded autonomy.](/skills/docker-agent-config/)[### Docker Agent deploy ↗ Pins Docker's agent serve, share, and eval skill, which refuses a non-loopback listener that has no auth token.](/skills/docker-agent-deploy/)[### Docker Agent run ↗ Pins Docker's skill for docker agent run, including the safety modes and the exception that a local stdio MCP server stays outside the sandbox VM.](/skills/docker-agent-run/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
