Docker Space Build Stuck — Empty Logs

Spaces
1

Docker Space Build Stuck — Empty Logs

Hi, I’m experiencing an issue where Docker Space builds are permanently stuck in BUILDING with completely empty build logs since today (March 26). The same setup was working fine yesterday.

What happens:

  • After pushing to a Docker Space, status shows BUILDING but build logs are completely empty — nothing appears at all.

  • The API shows hardware.current: null while hardware.requested: cpu-basic, so it seems no build machine is ever allocated.

  • Factory reboot has no effect.

What I’ve tried:

  • Deleting and recreating the Space multiple times

  • Creating a minimal test Space with just a 2-line Dockerfile (FROM python:3.11-slim + pip install streamlit) — same issue

  • Different Space names — same result

  • Token is valid and has repo.write permission (same token worked yesterday)

Additional issue: After deleting and recreating a Space with the same name, the API returns Invalid input: expected object, received undefined → at metadata/compute/service. This persists even on a freshly created Space with that reused name, suggesting the name gets corrupted in the backend after delete/recreate cycles.

Account: yc-lin-geo
Current affected Space: yc-lin-geo/ISMIP6-Antarctica-SLR-Explorer
Last successful build: March 25, 2026

1 Like
Stuck in starting [Docker Spaces]