Tag the latest docker build?
See original GitHub issue@garris loving the work youāre doing and we just started to use the docker image youāre providing. I noticed that you pushed a new docker image yesterday thatās got a slick new UI for the test results page. However itās currently available at the latest
tag in docker, so I canāt lock our project to that build. Is it possible to tag the current version in addition to having the latest
tag for those of us that canāt live on the bleeding edge?
Keep up the great work!
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to create named and latest tag in Docker? - Stack Overflow
Use: ID=$(docker build -q -t myrepo/myname:mytag . ) . The "-q" means only the ID is written to stdout. You should always specify...
Read more >docker tag
docker tag : An image name is made up of slash-separated name components, optionally prefixed by a registry hostname. The hostname must comply...
Read more >What's Wrong With The Docker :latest Tag? - vsupalov.com
It's just the tag which is applied to an image by default which does not have a tag. Those two commands will both...
Read more >The misunderstood Docker tag: latest | by Marc Campbell
To illustrate how the latest tag actually works, let's create a pretty basic Dockerfile. The contents of this are here:
Read more >Why can't I pull the newest image by using the latest tag?
The latest tag is applied to the most recent docker build or docker tag command that was run without a tag value explicitly...
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
BOOM. FIXED!
v3.1.17 just built itself.
Thanks again for reporting!
š