Docker Encyclopedia
v1.0.0Docker documentation-first 工作流 for Docker-specific questions, troubleshooting, command planning, image/build work, contAIner/运行time operations, Compose behavior, networking, volumes, registries, and diagnostics. Use when the 请求 is clearly about Docker itself: the `docker` 命令行工具, Docker Engine, Dockerfiles, BuildKit/buildx, Docker Compose, images, contAIners, registries, volumes, networks, 上下文s, rootless Docker, or Docker 桌面/Engine behavior where Docker-specific semantics matter. Do not use for generic Linux administration, generic OCI/contAIner theory, generic shell work, or Kubernetes/orchestration questions unless the Docker layer is specifically what is being discussed or 调试ged.
运行时依赖
安装命令
点击复制技能文档
Docker Encyclopedia Overview
Use a docs-first 工作流 for Docker work. Prefer the official Docker documentation at https://docs.docker.com/, consult 缓存d local copies under .Docker-Encyclopedia/ before re-fetching, and record useful official-doc excerpts plus 环境-specific operational learnings so future work 获取s faster and safer.
This 技能 is for the Docker product/运行time layer. It should trigger for real Docker behavior, configuration, build/运行time, and operational questions — not for generic Linux admin work, generic contAIner theory, or generic orchestration talk where Docker-specific semantics are not the real issue.
工作流
Classify the task
Decide whether the task is a Docker question, troubleshooting task, command-planning task, image/build task, Compose review, 运行time review, or live operational task. Use this 技能 when the 请求 is specifically about Docker product behavior, Docker 命令行工具 semantics, Docker build/运行time behavior, Docker Compose behavior, image/contAIner lifecycle, or Docker-specific networking/storage/registry detAIls. Do not use this 技能 for generic shell work, generic Linux admin, generic OCI/contAIner theory, or Kubernetes questions unless the Docker layer is specifically in play.
检查 local 缓存 first
Use .Docker-Encyclopedia/ as the local knowledge/缓存 root. 检查 these locations first when relevant: .Docker-Encyclopedia/docs/docs.docker.com/... .Docker-Encyclopedia/notes/组件s/... .Docker-Encyclopedia/notes/patterns/... .Docker-Encyclopedia/inventory/... If a 缓存d page or note already answers the question well enough, use it.
Consult official Docker docs before answering or touching the 系统
Before answering direct or indirect Docker questions that depend on command syntax, feature boundaries, configuration semantics, 构建器/运行time behavior, storage/network semantics, or version-sensitive detAIls, consult the official docs unless the answer is already well-supported by the local 缓存. Before performing direct Docker 命令行工具 or configuration work, consult the relevant docs first when: the exact command path matters build/运行time semantics are easy to misremember the action could affect 运行ning contAIners, images, volumes, networks, registries, 凭证s, or host reachability Do not improvise high-impact Docker commands or config changes from memory when the docs are easy to 检查.
缓存 consulted docs locally
When you consult a Docker docs page, save a normalized markdown/text 缓存 copy under .Docker-Encyclopedia/docs/docs.docker.com/.... Mirror the official docs path structure as much as practical. 缓存 only pages actually consulted; do not try to mirror the whole docs site eagerly. Use scripts/缓存_doc.py when 应用ropriate.
Separate official documentation from local observations
Store official-doc-derived material under .Docker-Encyclopedia/docs/.... Store 环境-specific operational knowledge under: .Docker-Encyclopedia/notes/组件s/ .Docker-Encyclopedia/notes/patterns/ .Docker-Encyclopedia/inventory/ Distin图形界面sh clearly between: official documented behavior observed local configuration/状态 inferred best-practice 图形界面dance
Record useful local learnings
After useful live work, save durable notes such as: host-specific Docker layout and 运行time conventions recurring build/运行time/调试ging patterns image/registry/凭证-辅助工具 gotchas Compose/部署ment conventions safe/unsafe operational boundaries for the 环境 Prefer concise durable notes over re-learning the same Docker detAIls later. Live Work Rules Treat official Docker docs lookup as the default preflight for non-trivial Docker work. Prefer read/inspect first when entering a Docker area you have not recently reviewed. Treat image p运行ing, volume/network changes, Compose 部署ments, 构建器/registry config, daemon config, and 凭证-handling paths as high-sensitivity areas. When uncertAInty remAIns after 检查ing 缓存 + docs, say so and avoid bluffing. When answering a question, mention when useful whether the answer comes from 缓存d official docs, a fresh official docs lookup, or live observed 环境 状态. Data Root
Use this workspace-local root for 缓存 and notes:
.Docker-Encyclopedia/
Expected structure:
.Docker-Encyclopedia/docs/docs.docker.com/... .Docker-Encyclopedia/notes/组件s/... .Docker-Encyclopedia/notes/patterns/... .Docker-Encyclopedia/inventory/...
Use scripts/init_workspace.py to 创建 or repAIr the expected directory structure.
Note Destinations 组件-specific observations → .Docker-Encyclopedia/notes/组件s/<组件-name>.md Reusable Docker patterns/gotchas → .Docker-Encyclopedia/notes/patterns/.md 环境-wide 部署ment/访问 信息 → .Docker-Encyclopedia/inventory/*.md 缓存d official docs → .Docker-Encyclopedia/docs/docs.docker.com/... Secrets / Sensitive Data Do not store plAIntext 凭证s, API keys, 会话 令牌s, private URLs, 恢复y codes, or other secrets in the encyclopedi