菜单
Docker Swarm deployment patterns covering stack deployments, networking, TLS certificates, NFS permissions, Portainer management, and GPU workloads. Use when deploying or managing Docker Swarm services.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | docker-swarm |
| description | Docker Swarm deployment patterns covering stack deployments, networking, TLS certificates, NFS permissions, Portainer management, and GPU workloads. Use when deploying or managing Docker Swarm services. |
docker stack deploy -c compose.yml <stack-name>
docker stack ls # List all stacks
docker stack services <stack-name> # List services in a stack
docker stack rm <stack-name> # Remove a stack
docker service logs <service> # View service logs
docker service update --force <service> # Force restart
*.apps.example.com -> <manager-ip> (for automatic resolution)When deploying services behind Traefik:
services:
myapp:
deploy:
labels:
- "traefik.enable=true"
- "traefik.http.routers.myapp.rule=Host(`myapp.apps.example.com`)"
- "traefik.http.routers.myapp.tls=true"
- "traefik.http.routers.myapp.tls.certresolver=letsencrypt"
- "traefik.http.services.myapp.loadbalancer.server.port=8080"
root_squash prevent containers running as root from writing filesdocker exec <container> id)ls -la /mnt/...)Example - running as specific user:
services:
traefik:
user: "1001:991" # Match file owner UID:GID
Use overlay networks for service-to-service communication:
networks:
app-network:
driver: overlay
attachable: true
Services on the same overlay network can reach each other by service name:
http://myservice:8080
Control where services run:
services:
myapp:
deploy:
placement:
constraints:
- node.role == manager
- node.labels.app.role == web
Label nodes for placement:
docker node update --label-add app.role=web <node-id>
docker node update --label-add gpu.type=nvidia <node-id>
For services requiring GPU access:
services:
gpu-service:
deploy:
placement:
constraints:
- node.labels.gpu.type == nvidia
resources:
reservations:
devices:
- capabilities: [gpu]
/etc/docker/daemon.json on GPU nodesIf Portainer shows "Unable to connect to Docker environment" after Docker restarts:
docker service update --force portainer_agent
Always include health checks in compose files:
services:
myapp:
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:8080/health"]
interval: 30s
timeout: 10s
retries: 3
start_period: 40s
Configure update behavior:
services:
myapp:
deploy:
update_config:
parallelism: 1
delay: 10s
failure_action: rollback
order: start-first
rollback_config:
parallelism: 1
delay: 5s
# Check service status
docker service ps <service> --no-trunc
# View service logs
docker service logs -f <service>
# Inspect service config
docker service inspect <service>
# Check node status
docker node ls
# Check what's running on a node
docker node ps <node-id>
Core Elixir language guidelines covering common pitfalls like list access, immutability, module organization, struct access, date/time handling, and OTP patterns. Use when writing or reviewing Elixir code.
Ecto best practices covering preloading, schema types, changeset validation, field access, security, and migration conventions. Use when working with Ecto schemas, changesets, queries, or migrations.
Best practices for testing Elixir applications with Ecto.SQL.Sandbox, including background process handling, Oban testing, and test output quality. Use when writing or reviewing Elixir tests.
Phoenix HEEx template rules covering interpolation syntax, form building, class lists, conditional rendering, comments, and common anti-patterns. Use when writing or reviewing HEEx templates.
Phoenix LiveView patterns covering streams, JavaScript interop (hooks, colocated scripts, push events), testing, and form handling. Use when building or reviewing LiveView features.
Phoenix 1.8 framework conventions covering layouts, routing, components, icons, forms, HTTP clients, and design file handling. Use when building or reviewing Phoenix web applications.