fix(recovery): quarantine corrupt docker metadata on boot
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 0s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Failing after 10m8s
CD Pipeline / build-and-deploy (push) Has been skipped
CD Pipeline / post-deploy-checks (push) Has been skipped

This commit is contained in:
Your Name
2026-06-30 18:02:43 +08:00
parent c9ef44e050
commit 66ec3c92e5
3 changed files with 112 additions and 4 deletions

View File

@@ -11,6 +11,7 @@
- StockPlatform public edge / API 已恢復:`https://stock.wooo.work/healthz=200``/api/healthz=200`;但 freshness / ingestion 仍 `status=not_configured`blocker `postgres_not_ready`
**source 修正**
- `awoooi-startup-110.sh` 新增 bounded Docker start、dockerd journal corrupt metadata ID 抽取、container metadata dir quarantine 與 TERM main process 後重啟 Docker 的受控恢復路徑,避免下次 dockerd 因 JSON metadata 損壞卡死 startup。
- `full-stack-cold-start-check.sh` 新增 registry 外部 `/v2/` gate 與 K3s `IMAGE_PULL_BLOCKED` / `REGISTRY_PULL_REFUSED_EVENTS` blocker。
- `full-stack-recovery-scorecard.sh` 新增 `CORE_REGISTRY_HTTPS_CODE``CORE_REGISTRY_HTTP_CODE``CORE_REGISTRY_READY``CORE_REGISTRY_BLOCKER`registry `:5000` 未就緒時不允許 `CORE_READY`