# Infinitely stuck on "starting" even with container running

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Finfinitely-stuck-on-starting-even-with-container-running%2F177041%3E%5C
**Category:** Spaces\
**Created:** [June 21, 2026, 4:34pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Finfinitely-stuck-on-starting-even-with-container-running%2F177041 "2026-06-21T16:34:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![OwenStOnge](https://avatars.discourse-cdn.com/v4/letter/o/3ec8ea/32.png) [@OwenStOnge](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FOwenStOnge)%5C
**Post date:** [June 21, 2026, 4:34pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Finfinitely-stuck-on-starting-even-with-container-running%2F177041%2F1 "2026-06-21T16:34:43Z")

</div>

My Docker (R/Shiny on `rocker/r2u`) Space builds successfully and the runtime log clearly reaches `Listening on http://0.0.0.0:7860, but the space never leaves 'starting' so I cannot access my app in any way even though there is no code issue. I have seen other posts with this problem and have seen people say its an issue on the side of HF and they need to fix it, I am mainly posting so that the issue gets more attention as the space is very important to my job. Thanks.`

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [June 21, 2026, 10:06pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Finfinitely-stuck-on-starting-even-with-container-running%2F177041%2F2 "2026-06-21T22:06:36Z")

</div>

Since this [is probably a glitch on the HF side this time, I recommend this workaround if you’re in a hurry](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-at-starting-health-checker-not-responding-june-20-2026%2F177005%2F18). Even if the code and other content are the same, it may work if the space has a different name (namespace).

---

<div class="post-metadata">

**Author:** ![HyannisHarborHawks](https://avatars.discourse-cdn.com/v4/letter/h/ecb155/32.png) [@HyannisHarborHawks](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FHyannisHarborHawks)%5C
**Post date:** [June 21, 2026, 10:49pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Finfinitely-stuck-on-starting-even-with-container-running%2F177041%2F3 "2026-06-21T22:49:59Z")

</div>

I duplicated it and now the duplicated space is infinitely starting too. It is not just for one space, it is for whatever space I try to upload, including a duplicated space.

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [June 22, 2026, 9:33am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Finfinitely-stuck-on-starting-even-with-container-running%2F177041%2F4 "2026-06-22T09:33:36Z")

</div>

If this was caused by the issue that started yesterday, I think it’s probably resolved now: [Space stuck at "Starting" - health checker not responding - June 20 2026 - #28 by hysts](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fspace-stuck-at-starting-health-checker-not-responding-june-20-2026%2F177005%2F28)
