Docker Space Runs Normally but Run Logs Only Show “Application Startup” Banner, No Container stdout/stderr
Hugging Face Forums [Unofficial]
March 4, 2026
Thanks for the troubleshooting guidance.
We followed your suggestion and deployed a probe build on our Docker Space:
- Space: Bin29/ManimCat
- Probe commit: 100c4b9
- Probe behavior: forced BOOT_STDOUT, BOOT_STDERR, and periodic HEARTBEAT_STDERR to stderr every 15s at container startup.
Observed results:
- Runtime is healthy:
- stage = RUNNING
- replicas = 1/1
- domain = READY
- App is serving traffic:
- GET /health returns 200 with redis=true, queue=true, openai=true
- Build logs are complete and normal.
- Run logs still show only:
- “===== Application Startup at … =====” and no probe lines (no BOOT/HEARTBEAT output at all).
So this looks like run-log forwarding/viewer path issue rather than app logging config. We have reverted the probe commit to restore normal behavior:
- Revert commit: 0a6c24b
Could you please check backend log forwarding for this Space (Bin29/ManimCat), especially around the timestamps when probe commit 100c4b9 was running?
Discussion in the ATmosphere