Apache Superset The last docker image doesn't work

Bug description

1. Run superset in docker sudo docker run --rm -p 8088:8088 --name ss -e SUPERSET_SECRET_KEY=1 apache/superset:v5.0.0
2. Create admin account sudo docker exec -it ss superset fab create-admin \ --username admin \ --password admin \ --email admin@superset.com \ --firstname John \ --lastname Smith
3. Visit http://127.0.0.1:8088 , then login with admin account.
4. BOOM!! Internal server error

Superset version

• docker image: apache/superset:v5.0.0

Browser

Chrome

Comment From: dosubot[bot]

Hi @cupen! I'm Dosu and I’m helping the superset team.

Superset 5.0.0 Docker images have some breaking changes and new requirements that can cause internal server errors if not handled. After starting the container and creating the admin user, you also need to run both superset db upgrade and superset init inside the container to ensure the database schema and permissions are up to date—skipping these steps is a common cause of 500 errors on login (source). You can do this with:

sudo docker exec -it ss superset db upgrade
sudo docker exec -it ss superset init

If you are using a database like Postgres or MySQL, make sure the required Python drivers (e.g., psycopg2 for Postgres) are installed, as recent images do not include them by default. You can add them via a requirements-local.txt file or by extending the Docker image (source).

If you still see errors, check the Superset logs in the container (docker logs ss) for specific stack traces—they will help pinpoint missing dependencies or migration issues. If you upgraded from a previous version, you may need to remove old Docker volumes to avoid migration conflicts (source).

Let me know if you see a specific error message in the logs!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

Comment From: hainenber

You'll need to initialize the DB if you wish to run Superset as standalone container.

Dosu's comment is correct. I'll be closing off this ticket as I verified manually and found no problem after the DB got initialized. If there's any concerns/queries, please comment it out.

Comment From: cupen

Well, yes. It works after sudo docker exec -it ss superset init. Thanks.