Bug description
The bug is that following the Quickstart guide installs 4.1.3, not 5.0.0 as expected.
Had to set the TAG env var to 5.0.0 to get the latest image As per https://github.com/apache/superset/blob/master/docker-compose-image-tag.yml#L27 the image pulled will either be TAG or latest-dev
x-superset-image: &superset-image apachesuperset.docker.scarf.sh/apache/superset:${TAG:-latest-dev}
Seems currently the latest-dev is pointing to 4.1.3 .. potentially as that is the latest release pushed as per #release-announcements latest posts
Started with a clean slate, removed all prior images
# no TAG env var set
echo $TAG
nil
# no docker images
docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
superset git:(master) git pull
superset git:(master) git checkout tags/5.0.0
superset git:(5.0.0) docker compose -f docker-compose-image-tag.yml up
superset git:(5.0.0) docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
apachesuperset.docker.scarf.sh/apache/superset latest-dev a78d442cb598 4 weeks ago 4.71GB
redis 7 49061c0de571 4 weeks ago 195MB
postgres 15 5ab68e212eab 2 months ago 628MB
superset git:(5.0.0) docker exec -it superset_app superset version
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Superset 4.1.3
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Setting TAG env var to 5.0.0 results in the correct install
superset git:(5.0.0) export TAG=5.0.0
superset git:(5.0.0) echo $TAG
5.0.0
superset git:(5.0.0) docker compose -f docker-compose-image-tag.yml up
superset git:(5.0.0) docker image ls
REPOSITORY TAG IMAGE ID CREATED SIZE
apachesuperset.docker.scarf.sh/apache/superset latest-dev a78d442cb598 4 weeks ago 4.71GB
redis 7 49061c0de571 4 weeks ago 195MB
apachesuperset.docker.scarf.sh/apache/superset 5.0.0 270e7ee9577b 6 weeks ago 3.57GB
postgres 15 5ab68e212eab 2 months ago 628MB
superset git:(5.0.0) docker exec -it superset_app superset version
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Superset 5.0.0
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Potential Solution
As per suggestion by @sfirke in slack
- Someone with our Docker Hub credentials should manually tag 5.0.0-dev as latest-dev
- We should see if anything needs to be fixed in the release process logic so that if the current version associated with latest is semantically greater than the one being released, it doesn't overwrite the tag
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]
You're correct—there's a confirmed issue where the latest-dev Docker tag is still pointing to 4.1.3 instead of 5.0.0, which means following the Quickstart guide without setting the TAG variable pulls the outdated version. This has been reported by other users as well, and the current workaround is to explicitly set TAG=5.0.0 (or your desired version) before running Docker Compose to ensure you get the correct image [source].
The Docker Compose setup defaults to latest-dev because the -dev images include required database drivers for the development environment, which aren't present in the lean latest or versioned images [source]. The release process is supposed to update these tags automatically via a GitHub Action, but if something goes wrong, maintainers can manually re-tag images using the GitHub UI [source].
Community suggestions include manually tagging 5.0.0-dev as latest-dev and reviewing the release automation to prevent older versions from overwriting newer tags. For now, specifying the version tag directly is the most reliable way to get the intended image.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
