Use only semver as image tag
See original GitHub issueCurrently, images on Docker hub are tagged like this:
prom/cloudwatch-exporter:cloudwatch_exporter-0.11.0
It would be nice, when it would look like this:
prom/cloudwatch-exporter:0.11.0
This tag should then also be pushed to quay.io which currently only has latest.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Using Semver for Docker Image Tags - Medium
Tag the image using a semver label, and push all individual version components separately. 2. Tag the image with a tag to indicate...
Read more >Tagging Docker image (SemVer) - Stack Overflow
In my experience, it's not a very good practice to tag your images with build numbers as part of your image "version". As...
Read more >Docker tags are not compatible with semver #1201 - GitHub
When I try to use a plus character, this happens... $ docker tag some-image blah:0.0.0+1 Error response from daemon: Illegal tag name (0.0.0+1): ......
Read more >Semantic Versioning for Containers | Docker and Containers
In a Docker repository, container images are not versioned; instead, they are "tagged", and it's up the publisher to determine which ...
Read more >How do you tag docker images? - Andy Dote
An interesting question came up at work today: how do you tag your Docker images? In previous projects, I've always used a short...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Please see and comment on #378 – this should™ start automatically publishing tagged versions to both Quay and Docker Hub, as well as clarify the README on this.
Thanks for fixing this!