{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihp7jyohaizvq5txtrtgxmn7k2exnyjtpxt3mnu2bis5gqg5bn33m",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mottmpa27ju2"
  },
  "path": "/t/space-stuck-at-starting-health-checker-not-responding-june-20-2026/177005?page=2#post_26",
  "publishedAt": "2026-06-22T00:46:13.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "@hysts"
  ],
  "textContent": "Same symptom here — Docker Space `hetchyy/quranic-universal-audio`.\n\nThe container boots cleanly (gunicorn `Listening at ``http://0.0.0.0:7860`, all\nworkers up) and serves HTTP 200 on the public domain for `/`, `/healthz`, and\n`/livez`. The image builds successfully (`Pushing image → DONE`). But the\nruntime API stays at `stage: APP_STARTING` / `BUILDING` with\n`replicas.current: 0 / requested: 1` and never reaches RUNNING — the runtime\nSHA is stale vs repo HEAD.\n\nTried: restart, factory reboot, pause→resume, a fresh no-op revision (built\nfine, never promoted), and a hardware toggle (froze in BUILDING ~15 min after\nthe build had already completed). Nothing promotes a replica.\n\n@hysts could you force-reconcile / reschedule this Space’s deployment if possible? Looks\nlike the same health-checker incident.",
  "title": "Space stuck at \"Starting\" - health checker not responding - June 20 2026"
}