CONTAINER SANDBOXES / Docker
Docker Sandboxes lifecycle
Pins Docker's local sbx lifecycle skill, which requires a dry-run before prune and forbids mounting a secrets file into the sandbox.
“Use this skill when creating, running, reattaching to, listing, stopping, or removing Docker Sandboxes (the standalone `sbx` CLI that runs AI coding agents in isolated microVMs), even if the user just says they want to "run claude in a sandbox", "isolate an agent from my repo", "give an agent its own git clone", or "clean up old sandboxes". Covers `sbx run`/`sbx create` (including the built-in agents claude, codex, cursor, devin, docker-agent, gemini, opencode, shell), workspace bind-mount vs `--clone` isolation, additional read-only workspaces, reattaching by `--name`, `sbx ls`/`stop`/`rm`/`prune`, `sbx exec`, `sbx cp`, and `sbx ports`.”
01 / THE REASONING
Why this made the selection.
- The catalogue already has Docker's destructive-guardrails and network-credentials skills and not this lifecycle file.
- The file requires sbx prune --dry-run before removal, limits --force to already-reviewed teardown, and says a read-only mount still exposes a secrets file.
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-lifecycle/SKILL.md
- README.md
- LICENSE
Our findings
- The skill says sbx prune removes only stopped sandboxes but is still irreversible, and that --dry-run must be read before a real prune.
- It says sbx rm deletes containers, state, and sandbox-scoped secrets, and that --force must not be a habit.
- It says a :ro workspace mount blocks writes but not reads, so a secrets file must not be mounted that way.
- It says the current source flag is --filter until=VALUE and that an older installed sbx may still show since=.
Not established by this review
- The resource was not executed and its tools were not called.
- sbx was not installed or run.
- No sandbox was created, pruned, or removed.
- The cited docker/sandboxes commit was not fetched.
- 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.
DOCUMENTED COMMAND
npx skills add docker/skills 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.
- The README quick start is the command above, and it says the command prompts for which skills and which agents to install.
- The same README shows a one-skill form only with --skill docker-compose-patterns, not with docker-sandboxes-lifecycle.
- The README also shows /plugin install docker-skills@docker after /plugin marketplace add docker/skills.
Before you start
- A skills-compatible agent or the skills CLI
- The standalone sbx CLI if the skill's commands are followed, which this review did not install
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-lifecycle/SKILL.md
Supports: dry-run before prune, --force limit, and secrets-mount refusal
- Repository README ↗Checked
https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/README.md
Supports: npx skills add docker/skills and Apache-2.0 statement
- Repository LICENSE ↗Checked
https://github.com/docker/skills/blob/f79172733725e2fd236343ee7b963c446ed85d09/LICENSE
Supports: Apache License Version 2.0
https://raw.githubusercontent.com/docker/skills/f79172733725e2fd236343ee7b963c446ed85d09/skills/docker-sandboxes-lifecycle/SKILL.md
Supports: upstreamDescription, review.notTested, review.reviewedAt
https://raw.githubusercontent.com/docker/skills/f79172733725e2fd236343ee7b963c446ed85d09/README.md
Supports: install.command