Private Docker Space stuck at “Build Queued” with no Docker build logs

Hugging Face users are reporting a recurring platform-side glitch in which Private Docker Space builds remain stuck at "Build Queued" with no Docker build logs, according to a July thread in which more than a dozen people hit the same pattern. The issue is tied to the build worker or scheduler not picking up the job at all rather than to anything in the user's Dockerfile, and a factory reboot does not help; affected users are advised to test a manual commit or a `git push` with a token instead of OIDC to isolate whether the Trusted Publishers/OIDC publishing path is stuck, and to include that result when escalating to website@huggingface.co.

This is a recurring platform-side glitch there’s a whole thread from July with a dozen+ people hitting the exact same “no logs at all, factory reboot doesn’t help” pattern, sometimes it self-resolves, sometimes not, and it’s tied to the build worker/scheduler not picking up the job at all rather than anything in your Dockerfile . Given yours also comes in through Trusted Publishers/OIDC specifically, worth testing whether a manual commit edit README directly on the Hub, or git push with a token instead of OIDC triggers a normal build, that’d isolate whether it’s the OIDC publishing path itself getting stuck vs. a general builder queue issue affecting everyone. If a manual push builds fine, that’s useful info to include when you escalate to website@huggingface.co mailto:website@huggingface.co , since it’d point at the Trusted Publishers integration specifically rather than a platform-wide outage.