Problem: Docker tags newer than 0.9.2 have an extra “-2” in them

[nano9g]

Versions

0.9.3, 0.9.4

Scope

Unknown

Issue

On Docker Hub, the 0.9.3 and newer tags contain a “-2”. This is problematic for those who pin to a version and use tools like Renovate (which is ignoring those tags because it can’t understand them without adding a configuration directive).

• 0.9.4-2-alpine
• 0.9.4-2-debian

If this is intentional and will be the new standard for Ansible-WebUI, I’ll update my Renovate config to account for it. I just wanted to ensure it wasn’t an accident.

Thanks!

[superstes]

Greetings.

Yeah - I had to release fixes to the major version as there have been breaking bugs.
As pypi/pip does not allow reuploads I have created these 'patched versions'.

Do you think it might maje more sense to omit those indicators for container images? I could just update my build-scripts to always build & push the 'simple version'.
I guess that would be more of a standardized versioning for images.. 🤔

[nano9g]

Do you think it might make more sense to omit those indicators for container images?

I agree that sticking to clean semantic versioning is going to be best for container images. Although there's no true standard for tags, most tools seem to handle major.minor.patch-description just fine while apparently some (like Renovate) can have difficulty with major.minor.patch-something-description without additional configuration.

If a re-release is required in the future, another idea to consider would be bumping the patch version on re-release. Although it might not technically be a New Version in the traditional sense, it does make it clear that something has changed and would keep versions aligned across pypi/pip and Docker. Ultimately, version numbers are all made up anyway. 😄