跳到主内容
智客 ZICQ

技能库 智客分类:运维与云 docker-production

Docker Production

Guidance for deploying Docker in production environments. Covers Docker Swarm (init, join, stack deploy, service scaling, rolling updates), Kubernetes migration (kompose conversion, Helm charts, differences), resource quotas and limits, zero-downtime deployment patterns, monitoring with cAdvisor + Prometheus + Grafana, Docker with systemd, and production hardening. Use when the user asks about production Docker, swarm, stack deploy, K8s migration, zero-downtime, container monitoring, or needs to deploy Docker in production. 使用场景:生产部署、docker swarm、docker stack、K8s迁移、零停机部署、容器监控、生产环境.

84 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

在生产环境中部署多克的指导. 覆盖 Docker Swarm (init, 加入, 堆栈部署, 服务缩放, 滚动更新), Kubernetes 迁移( kompose 转换, Helm 图表, 差异), 资源配额和限制, 零下限部署模式, 用 cAdvisor + Prometheus + Grafana 进行监控, 使用系统加固 Docker 和 生产加固

何时用

** 用户提到时总是使用这种技能:**

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Docker Production — 生产环境部署、When to Use、Docker Swarm Quick Start、Initialize cluster、Join workers (run on worker nodes)、Deploy a stack。 其中含规范建议的小节:输入输出示例。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

Docker Production — 生产环境部署When to UseDocker Swarm Quick StartInitialize clusterJoin workers (run on worker nodes)Deploy a stackManage servicesSwarm Compose ExampleZero-Downtime DeploymentKubernetes MigrationConvert compose to K8sOutput:

· 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
docker-production
description
Guidance for deploying Docker in production environments. Covers Docker Swarm (init, join, stack deploy, service scaling, rolling updates), Kubernetes migration (kompose conversion, Helm charts, differences), resource quotas and limits, zero-downtime deployment patterns, monitoring with cAdvisor + Prometheus + Grafana, Docker with systemd, and production hardening. Use when the user asks about production Docker, swarm, stack deploy, K8s migration, zero-downtime, container monitoring, or needs to deploy Docker in production. 使用场景:生产部署、docker swarm、docker stack、K8s迁移、零停机部署、容器监控、生产环境.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「docker-production」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-a250f1f1176244c2-%E7%A0%81%E5%A4%B4%E7%94%9F%E4%BA%A7.html
请存为 .cursor/skills/docker-production/SKILL.md 或 .claude/skills/docker-production/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/full-stack-skills/docker-skills' --list

npx skills add 'https://github.com/full-stack-skills/docker-skills' --skill 'docker-production'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: docker-production description: Guidance for deploying Docker in production environments. Covers Docker Swarm (init, join, stack deploy, service scaling, rolling updates), Kubernetes migration (kompose conversion, Helm charts, differences), resource quotas and limits, zero-downtime deployment patterns, monitoring with cAdvisor + Prometheus + Grafana, Docker with systemd, and production hardening. Use when the user asks about production Docker, swarm, stack deploy, K8s migration, zero-downtime, container monitoring, or needs to deploy Docker in production. 使用场景:生产部署、docker swarm、docker stack、K8s迁移、零停机部署、容器监控、生产环境. license: Apache-2.0 --- # Docker Production — 生产环境部署 Guidance for deploying and managing Docker in production. ## When to Use **ALWAYS use this skill when the user mentions:** - "生产部署", "production Docker" - "docker swarm", "docker stack", "swarm cluster" - "Kubernetes migration", "kompose", "K8s" - "零停机部署", "rolling update" - "容器监控", "监控", "Prometheus" ## Docker Swarm Quick Start ```bash # Initialize cluster docker swarm init --advertise-addr # Join workers (run on worker nodes) docker swarm join --token :2377 # Deploy a stack docker stack deploy -c docker-compose.yml myapp # Manage services docker service ls docker service scale myapp_web=5 docker service update --image myapp:v2 myapp_web docker service logs -f myapp_web ``` ### Swarm Compose Example ```yaml version: '3.8' services: web: image: myapp:${TAG:-latest} deploy: replicas: 3 update_config: parallelism: 1 delay: 10s order: start-first rollback_config: parallelism: 1 delay: 10s resources: limits: cpus: '0.5' memory: 512M ports: - "80:8080" ``` ## Zero-Downtime Deployment ``` Rolling Update Flow: ┌──────┐ ┌──────┐ ┌──────┐ Old replicas (v1) │ v1 │ │ v1 │ │ v1 │ └──────┘ └──────┘ └──────┘ docker service update --image myapp:v2 web Step 1: Start v2 ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ │ v1 │ │ v1 │ │ v1 │ │ v2 │ ← 1 new └──────┘ └──────┘ └──────┘ └──────┘ Step 2: Replace one v1 with v2 ┌──────┐ ┌──────┐ ┌──────┐ ┌──────┐ │ v1 │ │ v1 │ │ v2 │ │ v2 │ ← 2 new └──────┘ └──────┘ └──────┘ └──────┘ ... until all v2 ``` ## Kubernetes Migration ```bash # Convert compose to K8s kompose convert -f docker-compose.yml # Output: # web-deployment.yaml # web-service.yaml # ... # Apply kubectl apply -f . ``` | Compose | K8s | |---------|-----| | services | Deployments + Services | | networks | Network Policies | | volumes | PersistentVolumeClaims | | deploy.replicas | Deployment.spec.replicas | | secrets | Secrets | ## Monitoring Stack ### cAdvisor + Prometheus + Grafana ```yaml # docker-compose.monitoring.yml services: cadvisor: image: gcr.io/cadvisor/cadvisor:latest ports: ["8080:8080"] volumes: - /:/rootfs:ro - /var/run/docker.sock:/var/run/docker.sock:ro - /sys:/sys:ro prometheus: image: prom/prometheus:latest ports: ["9090:9090"] volumes: - ./prometheus.yml:/etc/prometheus/prometheus.yml grafana: image: grafana/grafana:latest ports: ["3000:3000"] ``` ## Workflow — 推荐部署流程 Step 1: **单机部署**: compose.yml + `restart: unless-stopped` + systemd 守护 Step 2: **Swarm 集群**: `docker swarm init` → `docker stack deploy -c compose.yml myapp` Step 3: **滚动更新**: `docker service update --image myapp:v2` + health check + rollback Step 4: **监控接入**: Prometheus + cAdvisor + Grafana 绑定额仪表盘 Step 5: **K8s 迁移**: `kompose convert` → 手动添加资源限制+健康检查 → Helm Chart ## Gotchas — Common Pitfalls - **Single Swarm manager**: If the only manager goes down, the cluster is unresponsive. → **Recovery**: Use 3 or 5 managers; `docker node promote ` to add manager; back up `/var/lib/docker/swarm/` regularly. - **Rolling update health check**: Without health checks, updates may deploy broken containers. → **Recovery**: Define HEALTHCHECK in Dockerfile + service health check; use `--update-failure-action rollback`. - **Data without volumes**: Production databases MUST use volumes. Container restart = new filesystem without volumes. → **Recovery**: `docker service create --mount type=volume,src=db_data,target=/var/lib/mysql`. - **Direct K8s migration**: `kompose` is a starting point, not production-ready K8s configs. → **Recovery**: After `kompose convert`, manually add resource limits, health checks, init containers, and ConfigMap/Secret references. ## Boundary — 能力边界(适用与不适用场景) | 分类 | 场景 | 说明 | |------|------|------| | ✅ 能做 | 单机 Compose 生产部署 | compose.yml + systemd 守护 | | ✅ 能做 | Swarm 集群管理 | init/join/stack deploy/rolling update | | ✅ 能做 | K8s 迁移方案 | kompose + 手动调整 + Helm Chart | | ✅ 能做 | 生产监控搭建 | Prometheus + cAdvisor + Grafana + Loki | | ⚠️ 需条件 | 多数据中心 Swarm | 需 overlay 网络 + 低延迟连接 | | ⚠️ 需条件 | 零停机迁移 K8s | 需蓝绿/金丝雀发布策略 | | ❌ 超范围 | 应用代码部署 | 各语言 CI/CD 管道 | | ❌ 超范围 | K8s 集群搭建 | 使用 K8s 官方文档 | | ❌ 超范围 | 数据库高可用 | DBA 专业领域 + 数据库原生方案 | ## When NOT to Use | ❌ Skip | ✅ Use Instead | |---------|---------------| | Development/debugging | `docker-run` | | Single-container apps | `docker-run` + systemd | | K8s-native from start | Skip Swarm, use K8s directly | | Docker basics | `docker-basics` | ## Security & Stability - Rotate Swarm join tokens regularly. Leaked worker tokens allow unauthorized node joining. - Use Docker Secrets for all sensitive configuration in production stacks. - Enable TLS for Docker daemon in production (`tlsverify` mode). - Implement resource limits on all production services to prevent noisy-neighbor issues. - Back up Swarm raft data regularly: `/var/lib/docker/swarm/`. - Monitor node health and set up alerts for node failures. ## 📚 官方文档参考 | 文档 | 地址 | |------|------| | Docker Swarm | https://docs.docker.com/engine/swarm/ | | Docker Stack | https://docs.docker.com/engine/swarm/stack-deploy/ | | 管理指南 | https://docs.docker.com/admin/ | | 生产环境 Compose | https://docs.docker.com/compose/production/ | | 安全部署 | https://docs.docker.com/engine/security/ | | Docker 引擎 | https://docs.docker.com/engine/ | ## 🧭 Docker Skills Journey > 📍 **You are here: `docker-production` — 生产部署** **← Previous**: `docker-cicd` | **→ Next**: `docker-troubleshooting` ## FAQ **Q1: 如何快速上手此技能?** A: 参考上方的快速开始章节,按步骤操作即可。 **Q2: 遇到版本不兼容问题怎么办?** A: 检查依赖版本,使用 lock 文件锁定,参考常见陷阱章节。 **Q3: 如何在生产环境使用?** A: 参考最佳实践章节,确保配置正确,做好监控和日志。 **Q4: 性能如何优化?** A: 参考性能优化相关文档,使用缓存、索引等手段。 **Q5: 如何贡献或反馈问题?** A: 在 GitHub 仓库提交 Issue 或 Pull Request。 **Q6: 是否支持中文?** A: 支持中文文档和中文注释,详见国内适配章节。

相关技能

运维与云

Docker Essentials

用于容器管理,图像操作,调试的基本道克命令和工作流程.

运维与云

Find Skills

从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…

运维与云

Microsoft Foundry

构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…

运维与云

Azure Deploy

执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…