Closed CleverMindDev closed 5 years ago
No it's just the auto tagging doesn't work on the quay.io and dockerhub automated builds.
Also if the versions become stale, old or unsupported or contain vulnerabilities then I usually delete them. Maybe I will tag the last two versions and maybe also implement a :stable tag.
It would be nice to be able to use at least a ":stable" tag.
For example, right now the current "latest" image has a big issue: https://github.com/yobasystems/alpine-mariadb/issues/24
And there is no way to use easily previous stable images
Next on the list. Manifest creation for auto arch version tag coming soon.
Think this is sorted.
Both :stable
and :10.3.16
are available now. Going forward with new versions they should be tagged and the old ones left for historical reasons unless there are multiple security vulnerabilities, in which case i'll delete the tags.
By checking the documentation
I am trying to specify the tag ":vX.X.X" as described in the documentation to build the correct image for the desired mariadb version.
For example I am using in the Dockerfile:
However it fails.
The only working tags are the ones described here
Am I doing something wrong ?