a75eb1965c
cd-apps's post-deploy `docker image prune` runs under `set -euo pipefail`
after the containers are already swapped, so when it collides with a
concurrent deploy/disk-maintenance prune ("Error response from daemon: a
prune operation is already running") it fails an otherwise-successful
deploy (observed on the #587 planner deploy). The cleanup is best-effort;
disk-maintenance.yml is the real image-prune safety net.
- cd-apps: `docker image prune -af || true`.
- disk-maintenance: tolerate the same collision on its prune; the disk-%
threshold check afterward stays the real failure gate.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| cd-apps.yml | ||
| cd-brouter.yml | ||
| cd-infra.yml | ||
| cd-staging.yml | ||
| ci.yml | ||
| dependabot-auto-fix.yml | ||
| disk-maintenance.yml | ||
| staging-cleanup.yml | ||
| update-visual-snapshots.yml | ||