Container Version and Tagging System: Understanding & Request for version-range-tags

[perahoky]

Hello,

sorry and no offense but i dont understand the versioning and tagging system that you use on lsio.

Example from linuxserver nextcloud image:
There are multiple different tag patterns:

• Why are there tags like "version-" (e,g, version-31.0.7")
• Why is there a second -only tag ?
• what are the counting number tags "0 - 999" (e.g. "109")
• there are only single version tags but not tags for the latest version of a release version range for example release version tag "31" which contains the most latest minor / patch level of this version e.g. "31.1.8".

i do understand that "ls123" stands for the linuxserver specific tagversion of the container build, not the version of the original software source within the container.
i do understand the platform specific tags like "arm" "amd64".

Requests:

• Would you like to write a few words into you FAQ which explains your tagging for newcomers, please?

• Would you like to add a (release-)version range specific tag which contains the latest update within a release version range like "31"(.0.0) which contains the latest 31 like "31.1.8"(-ls123) (ls-version too). This way we could keep same tag within compatible version ranges and dont accidently update "latest" and break some setup due to breaking changes or bugs. See nextcloud original docker tags.
  I dont think the existing "number only" tags are these version range tags.
  The version range tags could conflict with the old numbers-only-tags. Maybe a adapted solution could be used like "v31" or "latest 31".

For example at nextcloud:
tags:

• "31" (which gives 31.1.8-ls333)
• "31.0" (31.0.7-ls122)
• "31.1" (31.1.8-ls333)
• "31.0.7-ls111"
• "31.0.7-ls122"
• "31.1.8-ls222"
• "31.1.8-ls333"

This way i could simply use tag "31" for a new installation and keep updating this image tag and always get compatible versions. I dont need to search/edit new version tags but simply pull the new image. I dont want to use "latest" tag because it is not expectable which version it really contains for compatibility purpose. For example i cant see if "latest" contains the latest 32, I want to stay at version 31 with latest patch until i expect 32 to be (really) (seriously) stable.

Foe example in case i pull the official nextcloud tag "latest" i would get a seriously incompatible version (i cant update my nextcloud 29 instance because reasons) and break my installation. i wouldnt see that without inspecting the image in detail. And downgrading is not possible.

I think most people would be satisfied with "latest 31" and dont need "31.0." "31.1". This would ease updating and scripting. I dont need to always switch the tags anymore and can simply use "31" or similar.

Thank you for understanding and i hope you like / accept my proposal.
Sincerely

[drizuid]

I didn't read all of this, i merely skimmed it because it's been asked 100000 times.. i suggest taking a look at
https://www.linuxserver.io/blog/docker-tags-so-many-tags-so-little-time

we have no intention of changing what we do or how we do it.

[aptalca]

I'll just add that what the op is asking for is semver tagging. There is a section in that article that explains why relying on upstream semver is a bad idea for our images and why we strongly recommend against it.