Same here. @hysts
I can confirm that I am experiencing the same issue on my side.
I tested a newly created Docker Space with a minimal Streamlit application. The image builds successfully, but the Space remains stuck at “Starting”, and the container log shows only:
===== Application Startup =====
This appears to be the same issue reported in the following threads:
Overview:
- Multiple users started reporting the issue during the same time period.
- Both newly created and previously working Spaces are affected.
- Minimal applications using different frameworks and base images reproduce the issue.
- The image build completes successfully, but the Space becomes stuck during application startup.
- Some affected Spaces eventually report “Scheduling failure: unable to schedule”.
- In at least one report, the API shows hardware.current as null while cpu-basic remains requested.
Since the issue is reproducible with minimal applications across different users and Spaces, this looks more like a Hugging Face-side scheduling, hardware-allocation, or runtime infrastructure issue than an application-specific problem.
The public status page currently shows the service as operational, but this may be a partial issue affecting only Space startup or the free cpu-basic scheduling pool.