Bug description
Following the Quickstart, docker compose -f docker-compose-image-tag.yml up gives
superset_init | Successfully built apache_superset superset_init | Installing collected packages: apache_superset superset_init | Attempting uninstall: apache_superset superset_init | Found existing installation: apache_superset 4.1.3 superset_init | Uninstalling apache_superset-4.1.3: superset_init | Successfully uninstalled apache_superset-4.1.3 superset_init | Successfully installed apache_superset-4.1.3 superset_init | WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. superset_init | Skipping local overrides superset_init | Unknown Operation!!! superset_init | ###################################################################### superset_init | Init Step 1/4 [Starting] -- Applying DB migrations superset_init | ###################################################################### superset_init | /app/superset/config.py:42: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81. superset_init | import pkg_resources superset_init | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py] superset_init | 2025-07-23 15:58:48,709:INFO:superset.initialization:Setting database isolation level to READ COMMITTED superset_init | INFO [alembic.env] Starting the migration scripts. superset_init | INFO [alembic.runtime.migration] Context impl PostgresqlImpl. superset_init | INFO [alembic.runtime.migration] Will assume transactional DDL. superset_init | ERROR [flask_migrate] Error: Can't locate revision identified by '363a9b1e8992' superset_init exited with code 1 service "superset-init" didn't complete successfully: exit 1
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] 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 @Kkkassini! I'm Dosu and I’m helping the superset team.
The error Can't locate revision identified by '363a9b1e8992' usually means your database expects a migration that isn't present in your current codebase. This often happens if you have leftover Docker volumes from a previous Superset or PostgreSQL version, or if the migration history changed recently in the master branch (which is common in active development).
To fix this, remove your old Docker volumes so a fresh, compatible database is initialized:
docker compose -f docker-compose-image-tag.yml down -v
docker compose -f docker-compose-image-tag.yml up
This approach has resolved similar issues for others using the latest Superset with Docker Compose, especially after recent migration changes or PostgreSQL upgrades. For more details, see this discussion.
If you cloned the repo with --depth=1, make sure to fetch all tags with git fetch --tags before checking out a specific tag, though this is less likely to be the cause here.
If you continue to see the error, double-check that your codebase and Docker image are both up to date and from the same branch/tag, and that all migration scripts are present in superset/migrations/versions/.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: hainenber
From the logs, looks like you have an existing Superset installation in the past. Can you perform docker compose down --volumes to ensure an installation from scratch?
Comment From: rusackas
Moving this to a Discussion, since I think it's a help request rather than a Superset bug, and the comments are on point thus far for a solution :D