The docker image tagged latest does not deploy the latest stable version

[qiaofeng1227]

[qiaofeng1227]

I want to use docker-compose.yml to get a product version of superset, but the version is 0.0.0dev.
There is something wrong with my operation. Please help me. Thank you very much.

[qiaofeng1227]

I start superset follow the documentation:
https://superset.apache.org/docs/installation/installing-superset-using-docker-compose

[qqliang]

I ran into the same problem. I wanna know the version of superset in docker, which is convenient for development.

[youngsol]

change this line to

apache/superset:1.3.0

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[rusackas]

This is an old/stale issue, but I fear it may still be relevant. Any input @hughhhh / @craig-rueda ?

[Robin-Brandt]

I can confirm this issue still persists in the frontend on version 1.5.3

[sfirke]

What is the issue - that running a latest dev version shows 0.0.0dev in the UI? That doesn't feel like a bug necessarily but some of the friction here could be addressed by implementing a new tag like official and pointing people to that instead of latest, as discussed here: #22244

[JoeJordan1]

I can also confirm that this is still an issue. We also pull the latest version in docker, however the UI only shows 0.0.0dev. When looking in the running app, as explained here: #4634 I have checked both the package.json file and version_info.json but they also just list the version as 0.0.0dev.

I have recently upgraded superset to the latest 3.0.1 release, I believe, but I can't confirm whether the upgrade has worked, as I can't determine the version either prior to or after the upgrade. I think the only way to check is to trawl through the UI for features that may have been introduced, but this is by no means a reliable solution.

[sfirke]

The Superset build process was recently changed so that the latest docker tag should point to the latest official release. Right now that's 3.0.1. See Pull Request #25322. Unfortunately things still seem to need work here. I'm renaming the issue title to reflect the current problem, post-PR #25322.

I am comparing the contents of the latest image with the contents of the 3.0.1 image. They are not identical. The latest image was created 7 hours later on the same day (2023-10-18), it's bigger (1.29GB instead of 1.11GB), and most troubling when I switch from 3.0.1 to latest on the same metadata db the installation breaks due to an apparent database migration.

What Superset administrators can do: don't point to the latest image in your Docker or Kubernetes deployment, instead point to a specific release tag like 3.0.1.

What developers & the project can do: Have the latest tag be applied to the image so that 3.0.1 and latest are identical. Ideally latest is just functioning like an alias. This would mean that users see 3.0.1 as the version inside the UI.

[rusackas]

Tagging @mistercrunch to look into the relevance of this now that things have been tweaked significantly.

[mistercrunch]

I need docker hub push perms to re-publish or tag older releases! Currently it's only triggered by CI where the perms exist, and it's tricky to do since the GitHub action and docker logic is different in the old branches.

Question though, are we mostly caring about overall latest builds here?

Wondering if there's such thing as "major" and "micro" latest tags as in 3.0-latest (might point to 3.0.99), and 3-latest might point to 3.99.99

[mistercrunch]

Note that I documented the work that I did here https://github.com/apache/superset/pull/26923/files#diff-3d81145232d337c575e1626a0d209c2e9219a42ade8fd214499acc13d8dbe185 , but it only affects builds moving forward for now.

[rusackas]

Sounds like things are all fixed going forward, so we can likely close this out as an active issue. If anyone disagrees, we can certainly revisit/reopen as warranted.