{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreid44xqbqx5xj2ggyhb7zkry2zich6zjvtymqpa5bcryfynexbfkcm",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mg7inferlv32"
  },
  "path": "/t/docker-space-runs-normally-but-run-logs-only-show-application-startup-banner-no-container-stdout-stderr/173988#post_1",
  "publishedAt": "2026-03-04T02:39:41.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "https://bin29-manimcat.hf.space"
  ],
  "textContent": "Hi everyone,\n\nI’m encountering a strange issue with Hugging Face Spaces (Docker SDK) and would like to ask whether this might be a platform-side logging channel problem, or if I’ve misconfigured something on my end.\n\n**Space Details:**\n\n  * Space: Bin29/ManimCat\n  * SDK: docker\n  * Current running domain: https://bin29-manimcat.hf.space\n\n\n\n**Observed Behavior:**\n\n  1. Build logs are normal, with complete output (e.g., `npm run build`, `vite build`, `Pushing image`, etc.).\n  2. Runtime status appears healthy:\n     * `stage = RUNNING`\n     * `replicas.current = 1`\n     * Domain status: `READY`\n  3. Health checks pass:\n     * `GET /health` returns HTTP 200\n     * Response includes `redis=true`, `queue=true`, `openai=true`\n  4. However, run logs (both in the web UI and via API SSE) contain almost only one line:\n     * `===== Application Startup at ... =====`\n     * No subsequent application logs appear (container stdout/stderr seem not to be forwarded).\n\n\n\n**Key Points:**\n\n  * The service is not down; endpoints are accessible and health checks succeed.\n  * Business requests can be triggered and receive responses (e.g., 401 errors, etc.).\n  * Only the runtime log channel appears blank.\n\n\n\n**Troubleshooting Steps I’ve Taken:**\n\n  1. Checked runtime status via API:\n\n         from huggingface_hub import HfApi\n         api = HfApi(token=\"***\")\n         rt = api.get_space_runtime(\"Bin29/ManimCat\")\n         print(rt.stage, rt.raw)\n\n\nResult: `RUNNING`, domain `READY`.\n\n  2. Fetched build logs via API (content present):\n\n         curl -N -H \"Authorization: Bearer $HF_TOKEN\" \\\n         \"https://huggingface.co/api/spaces/Bin29/ManimCat/logs/build\"\n\n\n  3. Fetched run logs via API (only startup banner):\n\n         curl -N -H \"Authorization: Bearer $HF_TOKEN\" \\\n         \"https://huggingface.co/api/spaces/Bin29/ManimCat/logs/run\"\n\n\n  4. Accessed health endpoint:\n\n         curl -i https://bin29-manimcat.hf.space/health\n\n\nReturns `200 OK`.\n\n\n\n\n**Questions I’d Like to Confirm:**\n\n  1. Is this a known issue (e.g., Run logs SSE not forwarding container stdout/stderr)?\n  2. Are there any additional Docker Space configurations that could cause run logs to display only the platform banner?\n  3. Is there a way to trigger a “log channel reset” from the Space side (other than a factory reboot)?\n  4. Could the HF team check the log forwarder status for this Space from the backend?\n\n\n\n**Additional Notes:**\n\n  * I have already tried both `restart` and `factory reboot`.\n  * The build phase has always been normal; the issue is isolated to run logs visibility.\n\n\n\nIf anyone has encountered a similar situation, I’d greatly appreciate any debugging suggestions. Thank you!",
  "title": "Docker Space Runs Normally but Run Logs Only Show “Application Startup” Banner, No Container stdout/stderr"
}