GitHub user dosubot[bot] added a comment to the discussion: apache super set db migration issue
<!-- Answer --> Yes, your metadata DB at Alembic head `f5b5f88d8526` is fully compatible with Superset 6.0.0. You should use the official Docker image tag `apache/superset:6.0.0` for your containersājust set `TAG=6.0.0` in your `docker-compose-image-tag.yaml` before starting up. This will ensure your code and DB migrations are aligned, and you won't get Alembic errors when importing or running your database [source](https://github.com/apache/superset/pull/36680). The UI showing `0.0.0-dev` is just a cosmetic label from the frontend's `package.json` and doesn't affect DB compatibility. The real version is determined by the backend migrations and the Docker image you run [source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/package.json#L3-L3). If you use the official 6.0.0 image, the backend and migrations will match your DB, even if the UI still says `0.0.0-dev`. **Steps:** 1. Set `TAG=6.0.0` in your environment. 2. Run `docker compose -f docker-compose-image-tag.yaml up` to pull and start the correct image. 3. Confirm with `superset db current` that your DB is at `f5b5f88d8526`. 4. You should not see migration errors, and your data will be accessible. If you mount the local `docker/` directory, make sure your local code is also checked out at the `6.0.0` tag to avoid mismatches [source](https://github.com/apache/superset/issues/31510). Let me know if you need help with any manual steps after switching images (like re-entering DB passwords or cleaning up local mounts). <!-- 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/16f03958-870e-4d1a-b05f-b332ea018168?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/16f03958-870e-4d1a-b05f-b332ea018168?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/16f03958-870e-4d1a-b05f-b332ea018168?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/16f03958-870e-4d1a-b05f-b332ea018168?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/16f03958-870e-4d1a-b05f-b332ea018168?feedback_type=hallucination) | [Report š](https://app.dosu.dev/response-feedback/16f03958-870e-4d1a-b05f-b332ea018168?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/16f03958-870e-4d1a-b05f-b332ea018168?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Yes%2C%20your%20metadata%20DB%20at%20Alembic%20head%20%60f5b5f88d8526%60%20is%20fully%20compatible%20with%20Superset%206.0.0.%20You%20should%20use%20the%20official%20Docker%20image%20tag%20%60apache/superset%3A6.0.0%60%20for%20your%20containers%E2%80%94just%20set%20%60TAG%3D6.0.0%60%20in%20your%20%60docker-compose-image-tag.yaml%60%20before%20starting%20up.%20This%20will%20ensure%20your%20code%20and%20DB%20migrations%20are%20aligned%2C%20and%20you%20won%27t%20get%20Alembic%20errors%20when%20importing%20or%20running%20your%20database%20%5Bsource%5D%28https%3A//github.com/apache/superset/pull/36680%29.%0A%0AThe%20UI%20showing%20%600.0.0-dev%60%20is%20just%20a%20cosmetic%20label%20from%20the%20frontend%27s%20%60package.json%60%20and%20doesn%27t%20affect% 20DB%20compatibility.%20The%20real%20version%20is%20determined%20by%20the%20backend%20migrations%20and%20the%20Docker%20image%20you%20run%20%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/package.json%23L3-L3%29.%20If%20you%20use%20the%20official%206.0.0%20image%2C%20the%20backend%20and%20migrations%20will%20match%20your%20DB%2C%20even%20if%20the%20UI%20still%20says%20%600.0.0-dev%60.%0A%0A%2A%2ASteps%3A%2A%2A%0A1.%20Set%20%60TAG%3D6.0.0%60%20in%20your%20environment.%0A2.%20Run%20%60docker%20compose%20-f%20docker-compose-image-tag.yaml%20up%60%20to%20pull%20and%20start%20the%20correct%20image.%0A3.%20Confirm%20with%20%60superset%20db%20current%60%20that%20your%20DB%20is%20at%20%60f5b5f88d8526%60.%0A4.%20You%20should%20not%20see%20migration%20errors%2C%20and%20your%20data%20will%20be%20accessible.%0A%0AIf%20you%20mount%20the%20local%20%60docker/%60%20directory%2C%20make%20sure%20your%20local%20code%20is%20also%20chec ked%20out%20at%20the%20%606.0.0%60%20tag%20to%20avoid%20mismatches%20%5Bsource%5D%28https%3A//github.com/apache/superset/issues/31510%29.%0A%0ALet%20me%20know%20if%20you%20need%20help%20with%20any%20manual%20steps%20after%20switching%20images%20%28like%20re-entering%20DB%20passwords%20or%20cleaning%20up%20local%20mounts%29.) [](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/discussions/37232) GitHub link: https://github.com/apache/superset/discussions/37232#discussioncomment-15538784 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
