lasuite: halt retries pending Docker Hub creds (3rd rate-limit confirmation); pivot to M9
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
11
JOURNAL.md
11
JOURNAL.md
@ -720,3 +720,14 @@ prune fixed disk but forced re-pulls that hit Docker Hub's anonymous limit (A1 r
|
||||
finding, §1.5/§4.4). Recorded in STATUS ## Blocked + DECISIONS; surfaced to operator (provide Docker
|
||||
Hub creds). 5/6 recipes green via real !testme; lasuite install+backup green, upgrade gated.
|
||||
Pivoting to M9 (docs/reproducibility, unblocked) while the limit resets / creds arrive.
|
||||
|
||||
---
|
||||
## 2026-05-27 — lasuite quota-window retry insufficient; halting retries pending creds (3rd attempt)
|
||||
|
||||
Re-fired lasuite-docs !testme during the apparently-eased window (#96). The cached image redis:8.2.6
|
||||
gave "up to date", but the LATEST version's uncached redis:8.6.3 → `toomanyrequests` again. So the
|
||||
anonymous quota isn't reset enough for a full 9-service × 2-version deploy. Cancelled #96 + tore down
|
||||
clean. This is the 3rd confirmation the blocker is the Docker Hub rate limit. Per anti-thrash:
|
||||
**halting lasuite retries until the operator provides Docker Hub creds** (A1, STATUS ## Blocked).
|
||||
5/6 D10 recipes remain green via real !testme. Pivoting to M9 (docs/reproducibility) — fully
|
||||
unblocked, no image pulls.
|
||||
|
||||
Reference in New Issue
Block a user