Docker Compose
真实应用通常由多个服务组成:前端、后端API、数据库、缓存、消息队列。Compose让你用声明式方式管理这些服务。
# docker-compose.yml - 电商微服务 ✅
services:
# 前端
frontend:
build:
context: ./frontend
dockerfile: Dockerfile
ports:
- "3000:80"
depends_on:
- api
restart: unless-stopped
# API网关
api:
build:
context: ./api
dockerfile: Dockerfile
ports:
- "8000:8000"
environment:
DATABASE_URL: postgres://user:pass@db:5432/shop
REDIS_URL: redis://cache:6379
RABBITMQ_URL: amqp://mq:5672
depends_on:
db:
condition: service_healthy
cache:
condition: service_started
restart: unless-stopped
# PostgreSQL数据库
db:
image: postgres:16-alpine
environment:
POSTGRES_USER: user
POSTGRES_PASSWORD: pass
POSTGRES_DB: shop
volumes:
- pgdata:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U user -d shop"]
interval: 5s
timeout: 3s
retries: 5
restart: unless-stopped
# Redis缓存
cache:
image: redis:7-alpine
command: redis-server --maxmemory 256mb --maxmemory-policy allkeys-lru
restart: unless-stopped
# RabbitMQ消息队列
mq:
image: rabbitmq:3-management-alpine
ports:
- "15672:15672" # 管理界面
environment:
RABBITMQ_DEFAULT_USER: admin
RABBITMQ_DEFAULT_PASS: secret
restart: unless-stopped
volumes:
pgdata:
# depends_on 控制启动顺序 ✅
services:
api:
depends_on:
db:
condition: service_healthy # 等db健康检查通过
redis:
condition: service_started # 只等redis启动
# 健康检查配置
db:
healthcheck:
test: ["CMD-SHELL", "pg_isready"]
interval: 5s
timeout: 3s
start_period: 10s
retries: 5
# 启动3个API实例 ✅
docker compose up -d --scale api=3
# 在compose文件中指定
services:
api:
deploy:
replicas: 3
# 注意:使用scale时端口不能冲突
# 不指定宿主端口,让Docker分配
api:
ports:
- "8000" # 随机宿主端口
# 查看特定服务日志 ✅
docker compose logs api
# 进入服务容器
docker compose exec api bash
# 在运行的服务中执行一次性命令
docker compose run --rm api python manage.py migrate
# 重新构建并更新服务 ✅
docker compose up -d --build api
# 暂停/恢复服务
docker compose pause api
docker compose unpause api
# 查看资源使用
docker compose top
❓ depends_on能保证服务就绪吗?单纯
depends_on只保证启动顺序,不保证服务就绪。需要配合condition: service_healthy和healthcheck才能真正等待服务就绪。应用层也应该实现重试逻辑。❓ scale后负载均衡怎么配?Docker Compose内置DNS轮询负载均衡。同一服务的多个实例共享同一DNS名称,请求会轮询分配。生产环境建议在前面加Nginx/HAProxy做更精细的负载均衡。
| 要点 | 说明 | 最佳实践 |
|---|---|---|
| 资源规划 | 根据业务负载合理分配CPU/内存 | 先压测再上线,设置requests和limits |
| 监控告警 | 设置关键指标阈值和告警规则 | Prometheus + AlertManager,5分钟P99延迟告警 |
| 备份策略 | 定期备份关键数据和配置 | 自动化备份脚本 + 异地存储 + 定期恢复演练 |
| 灰度发布 | 新版本逐步放量降低风险 | 金丝雀发布5%→20%→50%→100% |
| 回滚预案 | 部署前确认回滚方案和步骤 | 保留前一版本镜像,数据库迁移向前兼容 |
| 文档更新 | 配置变更必须同步更新文档 | GitOps管理配置,变更即文档 |
| 安全基线 | 遵循CIS Docker Benchmark | 非root运行、只读FS、最小能力 |
| 日志规范 | 结构化日志,统一格式 | JSON格式日志,包含traceId |
# 容器生命周期
docker create/start/stop/restart/rm/pause/unpause
docker logs/top/stats/inspect/exec diff
# 镜像构建
docker build/pull/push/tag/rmi/images/history
docker save/load/import/manifest
# 网络与存储
docker network create/ls/inspect/connect/disconnect/rm/prune
docker volume create/ls/inspect/rm/prune
# Docker Compose
docker compose up/down/ps/logs/build/exec
docker compose config/stop/start/scale/top/cp
# 系统维护
docker system df/prune/info
docker builder prune
docker container/prune/image prune
# K8s常用命令
kubectl get/describe/logs/exec/apply/delete
kubectl rollout status/undo/history
kubectl scale/autoscale/set
version: "3.8" # Compose文件版本
services: # 服务定义(必填)
web:
image: nginx:alpine # 或 build: .
ports:
- "8080:80"
environment:
- KEY=VALUE
volumes:
- ./html:/usr/share/nginx/html:ro
networks:
- frontend
depends_on:
- api
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost/"]
interval: 30s
deploy:
replicas: 2
resources:
limits:
cpus: '0.5'
memory: 256M
restart: unless-stopped
networks: # 网络定义
frontend:
driver: bridge
volumes: # 卷定义
db-data:
secrets: # 密钥定义
db_password:
file: ./db_password.txt
configs: # 配置定义
nginx_config:
file: ./nginx.conf
# Step 1: 检查容器状态
docker ps -a # 查看所有容器
docker inspect <container> # 查看详细配置
# Step 2: 查看日志
docker logs --tail 100 <container> # 最近100行日志
docker logs --since 1h <container> # 最近1小时
# Step 3: 进入容器排查
docker exec -it <container> sh # 进入容器shell
# Step 4: 检查资源
docker stats --no-stream # 资源使用概览
docker system df # 磁盘使用
# Step 5: 网络排查
docker network ls # 网络列表
docker exec <c> ping <target> # 网络连通性
docker exec <c> nslookup <svc> # DNS解析
# Step 6: 检查健康状态
docker inspect --format '{{.State.Health}}' <c>
docker inspect --format '{{.State.ExitCode}}' <c>
docker inspect --format '{{.State.OOMKilled}}' <c>
# 通用最佳实践模板
FROM alpine:3.19 AS builder
# ... 构建步骤 ...
FROM alpine:3.19
RUN addgroup -S appgroup && adduser -S appuser -G appgroup
WORKDIR /app
COPY --from=builder /app/output .
USER appuser
HEALTHCHECK --interval=30s --timeout=3s --retries=3 \
CMD wget -qO- http://localhost:8080/health || exit 1
EXPOSE 8080
CMD ["./app"]
services:
app:
build: .
healthcheck:
test: ["CMD", "wget", "-qO-", "http://localhost:8080/health"]
interval: 30s
timeout: 5s
retries: 3
start_period: 30s
restart: unless-stopped
deploy:
resources:
limits:
cpus: '1'
memory: 512M