{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibb32borspox5qgt3jfpmcjnjg5q64d6eqrqshneegjkq34akdbty",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mg7pdgetjwh2"
  },
  "path": "/t/docker-space-runs-normally-but-run-logs-only-show-application-startup-banner-no-container-stdout-stderr/173988#post_5",
  "publishedAt": "2026-03-04T06:23:19.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "Thanks for the troubleshooting guidance.\n\nWe followed your suggestion and deployed a probe build on our Docker Space:\n\n  * Space: Bin29/ManimCat\n  * Probe commit: 100c4b9\n  * Probe behavior: forced BOOT_STDOUT, BOOT_STDERR, and periodic HEARTBEAT_STDERR to stderr every 15s at container\nstartup.\n\n\n\nObserved results:\n\n  1. Runtime is healthy:\n     * stage = RUNNING\n     * replicas = 1/1\n     * domain = READY\n  2. App is serving traffic:\n     * GET /health returns 200 with redis=true, queue=true, openai=true\n  3. Build logs are complete and normal.\n  4. Run logs still show only:\n     * “===== Application Startup at … =====”\nand no probe lines (no BOOT/HEARTBEAT output at all).\n\n\n\nSo this looks like run-log forwarding/viewer path issue rather than app logging config.\nWe have reverted the probe commit to restore normal behavior:\n\n  * Revert commit: 0a6c24b\n\n\n\nCould you please check backend log forwarding for this Space (Bin29/ManimCat), especially around the timestamps when\nprobe commit 100c4b9 was running?",
  "title": "Docker Space Runs Normally but Run Logs Only Show “Application Startup” Banner, No Container stdout/stderr"
}