Docker Eng
/install docker-eng
Docker Eng — Deep Workflow
Containers package applications with their dependencies. Optimize for small, reproducible images and clear runtime contracts—not “SSH into a mini VM.”
When to Offer This Workflow
Trigger conditions:
- Authoring Dockerfiles for apps or CI
- CVEs in base images; accidental secrets in layers
- Slow builds or oversized images pushing registry costs
Initial offer:
Use six stages: (1) base image & supply chain, (2) Dockerfile structure, (3) runtime config & secrets, (4) security hardening, (5) health & observability, (6) ops & debugging). Confirm registry and orchestrator (Kubernetes, ECS, etc.).
Stage 1: Base Image & Supply Chain
Goal: Pin tags or digests; prefer minimal bases (distroless, slim) when compatible.
Practices
- Scan images regularly (Trivy, Grype); track SBOM where required
Stage 2: Dockerfile Structure
Goal: Multi-stage builds: compile in builder, copy only artifacts to runtime; order layers for cache hits (dependency manifests before source).
Practices
- Maintain a robust
.dockerignore(exclude secrets, build artifacts, VCS noise)
Stage 3: Runtime Config & Secrets
Goal: Configuration via environment variables; secrets injected at runtime (K8s secrets, IAM, vault)—never COPY real secrets into the image.
Stage 4: Security Hardening
Goal: Run as non-root; read-only filesystem where possible; minimal packages in final image; avoid leaking build tools in production.
Stage 5: Health & Observability
Goal: HEALTHCHECK or orchestrator probes match real readiness (dependencies up); logs to stdout/stderr in structured form.
Stage 6: Ops & Debugging
Goal: Tag images with git SHA; document how to exec/debug (or use debug sidecars for distroless).
Final Review Checklist
- Base image pinned and scanned
- Multi-stage build; minimal runtime layer
- No secrets in layers
- Non-root and least privilege
- Health/readiness aligned with app
- .dockerignore and reproducible builds
Tips for Effective Guidance
- Explain layer caching order—why
COPY package.jsonbeforeCOPY .matters. - Distroless images: no shell—use ephemeral debug containers or sidecars.
Handling Deviations
- Windows containers: different paths and base images—validate separately.
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install docker-eng - 安装完成后,直接呼叫该 Skill 的名称或使用
/docker-eng触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
Docker Eng 是什么?
Deep Docker workflow—image design, multi-stage builds, security, runtime config, health checks, and operations. Use when containerizing apps, hardening image... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 127 次。
如何安装 Docker Eng?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install docker-eng」即可一键安装,无需额外配置。
Docker Eng 是免费的吗?
是的,Docker Eng 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。
Docker Eng 支持哪些平台?
Docker Eng 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 Docker Eng?
由 mikeclaw007(@mikeclaw007)开发并维护,当前版本 v1.0.0。