# Stuck in starting \[Docker Spaces\]
**URL:**
**Author:**  [@rossomalpelo](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Frossomalpelo)%5C
**Post date:** [December 14, 2024, 9:03am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F1 "2024-12-14T09:03:27Z")
## Introduction
I’ve set up a custom Docker space for a Discord bot. Currently, the bot doesn’t have AI capabilities and is only sending simple messages to users in the Discord server, which works as expected.
## Issue
However, the Docker space remains in a “starting” state, despite the bot functioning correctly. I suspect I’m missing a setting (required by 🤗 Spaces) that allows the Docker space to transition to a “running” state.
## Problem
This issue is problematic because the Docker container shuts down after the `startup_duration_timeout` expires.
## Question
Does anyone know what specific setting or response the Docker container needs to send to 🤗 space to change its status to “running”?
Thanks in advance!
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [December 14, 2024, 9:08am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F2 "2024-12-14T09:08:06Z")
To cut a long story short, it’s a bug or malfunction in HF Spaces. At the moment, there have been reports from at least 6 people, including you and me…😅
If you create a new space, it may take a while to work…
> **[Discord - Group Chat That’s All Fun & Games](https://discord.com/channels/879548962464493619/1317163404007571486)**
>
> Discord is great for playing games and chilling with friends, or even building a worldwide community. Customize your own space to talk, play, and hang out.
---
**Author:**  [@rossomalpelo](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Frossomalpelo)%5C
**Post date:** [December 14, 2024, 9:13am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F3 "2024-12-14T09:13:50Z")
Thanks for replying! Are you running a custom Docker space or does this happen with any other type of space, even the standard ones?
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [December 14, 2024, 9:16am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F4 "2024-12-14T09:16:00Z")
> even the standard ones?
YES.🤢 However, this is more likely to occur with Docker or private repositories. The sample size is small, so it may not be statistically significant, and it’s possible that it’s just in my head…
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [December 17, 2024, 2:07pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F5 "2024-12-17T14:07:50Z")
from HF Discord
> BC
> Hey I figured it out! I just rebuilt the space with a new streamlit version (1.41) since my previous one was on 1.31
```auto
pip install streamlit>=1.41
```
---
**Author:**  [@rossomalpelo](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Frossomalpelo)%5C
**Post date:** [December 22, 2024, 12:39pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F6 "2024-12-22T12:39:13Z")
I’m not using streamlit, so not sure this would help 🫠
---
**Author:**  [@DebasishDhal99](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FDebasishDhal99)%5C
**Post date:** [January 25, 2025, 6:46pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F7 "2025-01-25T18:46:15Z")
Since 15 minutes, my docker space is “Getting Started”
---
**Author:**  [@HuyRemy](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FHuyRemy)%5C
**Post date:** [March 26, 2026, 10:33am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F8 "2026-03-26T10:33:27Z")
Yes, I have that problem too, space stuck at starting and I fix it via Readme.md file, I add app\_port: 7860 to Readme.md file then it’s worked
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [March 26, 2026, 12:46pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F9 "2026-03-26T12:46:34Z")
Seems something is happening…
- [/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fall-spaces-failing-to-build-since-tuesday-no-logs-or-errors%2F174642%5D(https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fall-spaces-failing-to-build-since-tuesday-no-logs-or-errors%2F174642)
- [/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhf-space-stuck-at-restarting-no-error-logs%2F174648%5D(https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhf-space-stuck-at-restarting-no-error-logs%2F174648)
- [/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fdocker-space-build-stuck-empty-logs%2F174644%5D(https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fdocker-space-build-stuck-empty-logs%2F174644)
- [/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fmy-hugging-face-space-keep-starting%2F174616%5D(https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fmy-hugging-face-space-keep-starting%2F174616)
---
**Author:**  [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [March 26, 2026, 10:48pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-in-starting-docker-spaces%2F131043%2F10 "2026-03-26T22:48:31Z")
It appears that Hugging Face is currently investigating the matter internally.
> [@Stuck at space problem](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fstuck-at-space-problem%2F174654%2F3)%3A
>
> Thanks for the ping. Yeah, a similar issue has already been reported internally, and the infra team is currently working on it.