基础设施与运维
docker-compose-stack-error-handling
更新于 2026-07-23
Docker Compose · 错误处理规则
Error-handling rules for Docker Compose: classification, typed codes and single-point mapping to user outcomes.
- 技术栈
- Docker Compose
- 主题
- 错误处理
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Classify failures once: expected (validation, not-found) vs unexpected (bugs, dependencies down)
- ✓ Return typed errors carrying a stable code plus human-readable context
- ✓ Map errors to user-visible outcomes at the outermost layer only
✕ 常见反模式
- ✕ String matching on error messages to decide control flow
- ✕ Swallowing an error to keep the happy path green
- ✕ Leaking stack traces or internal identifiers to end users
◎ 交付前验证
- ◎ Image scanned and no new critical CVEs introduced
- ◎ Container exits cleanly on SIGTERM within the grace period
- ◎ Final image size compared against the previous build
同分类条目
38 篇基础设施与运维
Docker 工程规则
Production Dockerfile rules: minimal multi-stage images and non-root runtime
基础设施与运维
Docker Compose 工程规则
Compose rules: explicit healthchecks, pinned images and network segmentation
基础设施与运维
Kubernetes 工程规则
Kubernetes rules: resource limits, readiness probes and rolling-update safety
基础设施与运维
Helm 工程规则
Helm rules: values schema validation and template-time guard rails
基础设施与运维
Terraform 工程规则
Terraform rules: locked remote state, reviewed plans and no console drift
基础设施与运维
Ansible 工程规则
Ansible rules: idempotent tasks, changed_when discipline and vaulted secrets