All my Docker Spaces are stuck and never finish building. The build log only ever shows the queued line and never progresses to a running container, e.g.:
Things I’ve already ruled out, which point to an account/infra issue rather than my code:
Factory rebuild and restart do not help.
Reverting to a known-good commit that built successfully before does NOT help — same commit is now stuck.
I created a brand-new empty Space with a one-line Dockerfile (FROM python:3.11-slim + CMD [“python”,“-m”,“http.server”,“7860”]) and it ALSO stays stuck — so it’s not specific to any repo.
The exact same image builds and runs fine locally (docker build + docker run -p 7860:7860).
Same, none of my Spaces will build. Even one that was running perfectly fine and I did a Factory Build on it just to test and it stays stuck on Building.
I am facing same issue with HF spaces. None of the space is getting docker build for me. All of those gets stuck with “No Logs” message in the build section for image build using docker.
+1 — same issue. Space manishvishist/deepcover2 (PRO account), production site is down. Build stuck at “Build Queued”, never picks up a worker. Restart, factory-rebuild, and reverting to a known-good commit all do NOT help — exactly as described. Please prioritize, this is a live production Space.
Same issue here with Gradio SDK Spaces on free CPU-basic — so it’s not limited to Docker or ZeroGPU. Build logs stay empty and the API shows "hardware": {"current": null} forever. Factory reboot, duplicating, and a brand-new minimal test Space all stuck the same way. A previously built Space restarts fine, so only the build pipeline is affected.
I have the exact same issue everything is stuck at building when I try to use somebody’s spaces it says something about falling back to IP and not using my credits or nothing Something is really really wrong and it’s been going on for about two days if they ain’t got it fixed by in the morning I’m doing a chargeback because I thought I was legitly out of money and put 20 bucks in it and it was already 19 in it and I still can’t use it so that ain’t gonna happen especially can’t get done what I needed to do’cause I on a deadline for a project that I was relying on this for
Same here, on a PRO account — adding two data points that may help the team narrow it down:
**Existing docker Space — builds never START:** an existing docker Space of mine (cpu-basic; happy to share the exact name privately). Since 2026-07-16 22:26 UTC no build ever starts: stage stays RUNNING_BUILDING, Build log showed only “Build Queued at 22:48:50” and later just “No logs”. Tried factory reboot via API, UI “Restart space”, UI “Factory rebuild”, and a real git commit to the Space repo — nothing gets picked up. The previously running app keeps serving fine.
**Brand-new docker Space — build starts but never FINISHES:** created `builder-test-tmp` (Streamlit docker template) at ~05:57 UTC as a control test. A builder picked it up within seconds, but it has been “Building” for 30+ minutes with no completion.
So existing Spaces never start a build, and new Spaces start but don’t finish. The status page still shows all services operational — an acknowledgment there would help a lot. Thanks!