Stuck in starting [Docker Spaces]

Spaces
1

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 :hugs: 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 :hugs: space to change its status to “running”?

Thanks in advance!

1 Like
2

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…:sweat_smile:
If you create a new space, it may take a while to work…

3

Thanks for replying! Are you running a custom Docker space or does this happen with any other type of space, even the standard ones?

1 Like
4

even the standard ones?

YES.:nauseated_face: 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…

1 Like
5

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

pip install streamlit>=1.41