Docker release tagging

[davelowndes]

I don't understand the docker release tagging. I had an image running using apache/superset:5.0.0, but this is now gone and my stack fails to build. https://superset.apache.org/docs/installation/docker-builds/ says there should be a release tag but I don't see any. #30919 comments that "4.1.1 docker image are up so those can now be used." but I don't find any 4.1.1 tag.

So how do we get a stable tag for our docker images?

[dosubot[bot]]

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

There’s currently a confirmed issue with Docker image tagging for Superset: the latest-dev tag is still pointing to an older version (4.1.3) instead of 5.0.0, which can cause stacks to pull outdated images if you don’t specify a version. The release process is supposed to update these tags automatically, but if it fails, maintainers have to manually re-tag images, and sometimes this lags behind documentation updates. There’s also no official release tag in use, despite what the docs might suggest—stable images are published under versioned tags like 5.0.0 or 4.1.1 when available, but these can sometimes be missing or delayed due to CI/CD hiccups or manual intervention needs [source].

The most reliable way to get a stable Docker image is to explicitly set the TAG variable to the version you want (for example, export TAG=5.0.0), then run your Docker Compose or pull command. For docker-compose setups that need database drivers, use the -dev suffixed tags (like 5.0.0-dev or latest-dev) [source].

If a versioned tag you expect is missing, it’s likely due to a temporary issue with the release automation. You can check available tags on Docker Hub or by running docker pull apache/superset:<tag> to see if it exists. For now, always specify the version tag directly to avoid surprises.

To reply, just mention @dosu.

---

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