Bug description
I'm creating a server of apache superset with docker compose, but I have one container "superset-init" that doesn't work properly.
The server is on Ubuntu 24.04.2 LTS and has been created for this installation, so it contains nothing else.
My installation is a 5.0.0 standard, I don't change anything.
When I start containers, I have this error on superset-init :
With a "docker compose logs -f" command I have this :
I managed to get the server to work at the beginning of the week, I added the following line at the top of docker/docker-bootstrap.sh :
sleep 60
Now, even if I keep this line I also have the problem so I'm thinkings it's useless.
This morning I have to restart the compose, because I have to add a SUPERSET_APP_ROOT environment variable, but the container superset-init no longer wants to start...
Do you have any idea to help me ?
Thank you.
Screenshots/recordings
No response
Superset version
5.0.0
Python version
3.9
Node version
16
Browser
Firefox
Additional context
No response
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.
Comment From: dosubot[bot]
Hi @aklein-1s! I'm Dosu and I’m helping the superset team.
Your error is a known migration issue in Superset 5.0.0: the database expects a migration revision (74ad1125881c) that was present in earlier release candidates but removed in the final release. This usually happens if there are leftover Docker volumes from a previous install or if the migration history changed. The most reliable fix is to remove your old Docker volumes and start fresh:
docker compose down -v
docker compose up
This will reset the metadata database and allow migrations to run cleanly. If you need to preserve your data, back up your metadata database before running these commands. If you still see the missing revision error, you can manually fix the migration state by running:
docker compose run --rm superset superset db downgrade 74ad1125881c
docker compose run --rm superset superset db upgrade
docker compose run --rm superset superset init
The SUPERSET_APP_ROOT variable only affects URL generation (like OAuth login links) and is not related to migration failures, but make sure it is set correctly for your deployment path details.
If the problem persists, double-check that your Docker images and code are from the same version/tag and that all migration scripts are present in superset/migrations/versions/ reference reference reference.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: rusackas
The bot is 100% correct! Closing this, but happy to reopen as a Discussion if further help is needed.