← Explore all 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.

“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).”

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.

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 ↗

DOCUMENTED COMMAND

npx skills add docker/skills/skills/docker-sandboxes-network-credentials

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
  1. Install the pinned skill directory interactively, retaining its bundled references and scripts.
  2. Identify the standalone CLI and target sandbox, then inspect policy before changing rules.
  3. 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

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. Pinned skill definition ↗Checked

    https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials/SKILL.md

    Supports: summary, whySelected, bestFor, limitations, install, access, review

  2. https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/README.md

    Supports: install

  3. Apache-2.0 licence ↗Checked

    https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/LICENSE

    Supports: license

  4. https://raw.githubusercontent.com/docker/skills/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-network-credentials/SKILL.md

    Supports: upstreamDescription, review.notTested, review.reviewedAt, review.findings

Evidence & Ask