dasarikd0805-a11y opened a new issue, #35502:
URL: https://github.com/apache/superset/issues/35502

   ### Bug description
   
   The superset_init container exits after some time (~360s) and shows 
unhealthy, even though Superset itself works and login is successful.
   
   I cloned the Superset repository (branch 5.0.0) and ran docker compose -f 
docker-compose-image-tag.yml up. After starting the containers, I checked their 
status using docker ps and docker-compose ps. I observed that the superset_init 
container shows as Exited and unhealthy, even though the Superset UI is 
accessible and I am able to log in without any issues.
   
   ### Screenshots/recordings
   
   Please find attached the superset_init container logs along with environment 
details for reference.
   
   Environment details:
   
   [docker logs 
superset_init.txt](https://github.com/user-attachments/files/22692090/docker.logs.superset_init.txt)
   
   OS: Ubuntu 24.04.3 LTS running via Windows 10 Pro (22H2, Build 19045.6396)
   Superset version: 5.0.0
   Python version (inside container): 3.10.18
   Flask version: 2.3.3
   Werkzeug version: 3.1.3
   Docker version: 28.4.0, build d8eb465
   Docker Compose version: v2.39.4-desktop.1
   
   ### Superset version
   
   5.0.0
   
   ### Python version
   
   3.10
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   No feature flags or customizations enabled.
   This occurs on a fresh setup with default docker-compose.
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to