Use Forgejo's official mirror for recovery image pulls #701
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#701
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
During the 2026-07-31 disk-pressure incident, the Forgejo pod could not recover because codeberg.org returned HTTP 503 for the pinned 15.0.2-rootless image. The official data.forgejo.org mirror returned the exact OCI manifest successfully from kai-server. Change the tracked Forgejo Deployment to that mirror, validate the live diff is image-only, verify rollout readiness and public health, and retain infrastructure#624 for the recurring upload-staging and build-cache root cause.