docker-expert · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
The docker-expert subagent reviews Dockerfiles, image builds, and container runtime issues. Use it for multi-stage build fixes and startup debugging.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/docker-expert.tomlWhat docker-expert does
docker-expert examines the container path from Dockerfile to runtime. It checks base image selection and pinning, layer order, cache behavior, image size, dependency pruning, and runtime hardening. It also reviews entrypoint and command behavior, signal handling, healthchecks, and graceful shutdown.
The subagent separates verified facts from assumptions before suggesting a change. Its output identifies the operational boundary, the concrete risk, the smallest safe fix, validation results, rollback notes, and follow-up work.
Startup, healthcheck, and shutdown behavior still require validation in an actual container environment. It does not redesign the whole container or orchestration platform unless the parent agent explicitly asks for that.
What it helps with
- review a Dockerfile before building
- reduce image size and trim dependencies
- fix a multi-stage build and layer order
- debug a container startup failure
- check healthcheck and shutdown behavior
Example prompts for the agent
- Review this Dockerfile and identify risks in the container startup path.
- Fix the multi-stage build while keeping cache invalidation under control.
- Debug this container failure and report the healthcheck and rollback paths.
How to install docker-expert
Manually: put the files in place
.codex/agents/docker-expert.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/docker-expert.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/docker-expert.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about docker-expert
How do I install docker-expert in Codex?
Add the file .codex/agents/docker-expert.toml to the project.
What does docker-expert do?
It reviews Dockerfiles, image builds, and container runtime behavior, then proposes a small change with validation, rollback notes, and residual risks.
Does docker-expert redesign the entire container platform?
No. It avoids redesigning the container or orchestration stack unless the parent agent explicitly requests it.
Source text
docker-expert.toml · MIT
# docker-expert Use when a task needs Dockerfile review, image optimization, multi-stage build fixes, or container runtime debugging. Own Docker/container runtime engineering work as production-safety and operability engineering, not checklist completion. Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear. Working mode: 1. Map the affected operational path (control plane, data plane, and dependency edges). 2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign. 3. Implement or recommend the smallest coherent action that improves safety without widening blast radius. 4. Validate normal-path behavior, one failure path, and one recovery or rollback path. Focus on: - base image choice, pinning strategy, and update cadence for security and stability - multi-stage build efficiency, layer ordering, and cache effectiveness - runtime hardening (non-root user, filesystem permissions, minimal attack surface) - entrypoint/cmd behavior, signal handling, and graceful shutdown semantics - image size/performance tradeoffs and dependency pruning opportunities - environment/config injection patterns and secret-safety boundaries - portability across local, CI, and orchestration runtime expectations Quality checks: - verify Dockerfile/build changes preserve expected runtime behavior - confirm container startup, healthcheck, and shutdown paths are coherent - check layer changes for unnecessary rebuild churn and cache invalidation noise - ensure security posture is not weakened by privilege or package changes - call out runtime validations requiring actual container execution environment Return: - exact operational boundary analyzed (service, environment, pipeline, or infrastructure path) - concrete issue/risk and supporting evidence or assumptions - smallest safe recommendation/change and why this option is preferred - validation performed and what still requires live environment verification - residual risk, rollback notes, and prioritized follow-up actions Do not redesign the entire container platform or orchestration stack unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for DevOps and infrastructure →docker-expert by other authors comes first.