Latest tag on dockerhub points to snapshot instead of latest stable
See original GitHub issueCurrent Behavior:
On registry dockerhub registry:
dependencytrack/apiserver:latest
image has digest 4d9653d477fe
which corresponds to dependencytrack/apiserver:snapshot
image
Expected Behavior:
dependencytrack/apiserver:latest
should point to latest stable version, namely dependencytrack/apiserver:4.5.0
as of today
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
What's Wrong With The Docker :latest Tag? - vsupalov.com
Latest is Just a Tag ¶ ... Some people expect that :latest always points to the most-recently-pushed version of an image. That's not...
Read more >The misunderstood Docker tag: latest | by Marc Campbell
Docker images have a tag named latest which doesn't work as you expect. ... to Docker Hub, I'm going to build, tag and...
Read more >Understanding Docker's “latest” Tag - How-To Geek
Docker tags are used to identify images by name. Each image can have multiple tags assigned. Tags look similar to my-image:latest, with the ......
Read more >Docker Tagging: Best practices for tagging and versioning ...
Notice the original tags are now pointing to the new digests (3rp, 1n4) ... rather stable implies the image should be stable, for...
Read more >Container Image Versioning
A common practice is to tag every release with :latest independent if it is a development snapshot or the final release. Every successful...
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 FreeTop 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
Top GitHub Comments
For testing purposes I created the
dependencytrack/apiserver:issue-1644
tag from the currentdependencytrack/apiserver:snapshot
tag:and it worked as expected: https://hub.docker.com/layers/217931103/dependencytrack/apiserver/issue-1644/images/sha256-63c092bc4be6720199a68f864fc7fd4cb71ea2a1b3097426b9fa1db7a732df06?context=repo
Both platfoms are included and the image digests match. So we can “repair” the
latest
tag this way.@stevespringett
currently you will have to re-tag and push
latest
manually on your machine.i.e. (assuming you use Docker or Podman locally)
sorry for missing the latest tag logic in the original CI, but your changes cause the latest tag to follow the edge development on the default branch.
I will be doing more CI work this weekend / later today, so I will get on fixing this ASAP