You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dasarikd0805-a11y (via GitHub)" <gi...@apache.org> on 2025/10/04 05:43:19 UTC
[I] superset_init container exits as unhealthy despite successful Superset login [superset]
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: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] superset_init container exits as unhealthy despite successful Superset login [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #35502:
URL: https://github.com/apache/superset/issues/35502#issuecomment-3544295959
Anyone still facing this?
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] superset_init container exits as unhealthy despite successful Superset login [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #35502:
URL: https://github.com/apache/superset/issues/35502#issuecomment-4748480886
The superset_init container is a one-shot initialization job. It's expected to exit after it finishes, and Superset works normally afterward. Closing as working-as-designed, but please comment if init is actually failing rather than just exiting.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] superset_init container exits as unhealthy despite successful Superset login [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #35502:
URL: https://github.com/apache/superset/issues/35502#issuecomment-3367930366
<!-- Greeting -->
Hi @dasarikd0805-a11y! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
This is expected behavior for the superset_init container in Superset's Docker Compose setup. The container is designed to run a one-time initialization script (applying DB migrations, creating the admin user, setting up roles/permissions, and optionally loading example data), then exit. Its healthcheck is disabled, so Docker may show it as "exited" or "unhealthy" simply because it is no longer running, not because of an error. As long as Superset is working and you can log in, you can safely ignore the superset_init container's status—this is confirmed by the official configuration and documentation ([docker-compose-image-tag.yml](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker-compose-image-tag.yml), [docker-init.sh](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/docker-init.sh), [docs](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docs/docs/installation/docker-c
ompose.mdx)).
Unless you see explicit errors or non-zero exit codes in the superset_init logs, the "unhealthy" or "exited" state is benign and expected for this container.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/f0fac809-11af-4545-9afa-6838017a85f4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f0fac809-11af-4545-9afa-6838017a85f4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f0fac809-11af-4545-9afa-6838017a85f4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f0fac809-11af-4545-9afa-6838017a85f4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f0fac809-11af-4545-9afa-6838017a85f4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f0fac809-11af-4545-9afa-6838017a85f4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f0fac809-11af-4545-9afa-6838017a85f4?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/35502)
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] superset_init container exits as unhealthy despite successful Superset login [superset]
Posted by "sadpandajoe (via GitHub)" <gi...@apache.org>.
sadpandajoe commented on issue #35502:
URL: https://github.com/apache/superset/issues/35502#issuecomment-3372931377
@mistercrunch this is with `5.0` which we will continue to support after `6.0` is released. Do you know off the top of your head on why this might be happening?
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] superset_init container exits as unhealthy despite successful Superset login [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #35502: superset_init container exits as unhealthy despite successful Superset login
URL: https://github.com/apache/superset/issues/35502
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org