Docker Space Runs Normally but Run Logs Only Show “Application Startup” Banner, No Container stdout/stderr

Hi everyone,

I’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.

Space Details:

• Space: Bin29/ManimCat
• SDK: docker
• Current running domain: https://bin29-manimcat.hf.space

Observed Behavior:

1. Build logs are normal, with complete output (e.g., npm run build, vite build, Pushing image, etc.).
2. Runtime status appears healthy:
   • stage = RUNNING
   • replicas.current = 1
   • Domain status: READY
3. Health checks pass:
   • GET /health returns HTTP 200
   • Response includes redis=true, queue=true, openai=true
4. However, run logs (both in the web UI and via API SSE) contain almost only one line:
   • ===== Application Startup at ... =====
   • No subsequent application logs appear (container stdout/stderr seem not to be forwarded).

Key Points:

• The service is not down; endpoints are accessible and health checks succeed.
• Business requests can be triggered and receive responses (e.g., 401 errors, etc.).
• Only the runtime log channel appears blank.

Troubleshooting Steps I’ve Taken:

1. Checked runtime status via API:

   from huggingface_hub import HfApi
   api = HfApi(token="***")
   rt = api.get_space_runtime("Bin29/ManimCat")
   print(rt.stage, rt.raw)
   

Result: RUNNING, domain READY.

1. Fetched build logs via API (content present):

   curl -N -H "Authorization: Bearer $HF_TOKEN" \
   "https://huggingface.co/api/spaces/Bin29/ManimCat/logs/build"
   

2. Fetched run logs via API (only startup banner):

   curl -N -H "Authorization: Bearer $HF_TOKEN" \
   "https://huggingface.co/api/spaces/Bin29/ManimCat/logs/run"
   

3. Accessed health endpoint:

   curl -i https://bin29-manimcat.hf.space/health
   

Returns 200 OK.

Questions I’d Like to Confirm:

1. Is this a known issue (e.g., Run logs SSE not forwarding container stdout/stderr)?
2. Are there any additional Docker Space configurations that could cause run logs to display only the platform banner?
3. Is there a way to trigger a “log channel reset” from the Space side (other than a factory reboot)?
4. Could the HF team check the log forwarder status for this Space from the backend?

Additional Notes:

• I have already tried both restart and factory reboot.
• The build phase has always been normal; the issue is isolated to run logs visibility.

If anyone has encountered a similar situation, I’d greatly appreciate any debugging suggestions. Thank you!