Make default image tag `latest` (or None) for Docker storage
See original GitHub issueRight now the image name and image tag are both random UUIDs. While this does mean that collisions are on the order of (1 / the atoms in the universe) / the atoms in the universe
, having a random tag is probably redundant.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
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 >How to create named and latest tag in Docker? - Stack Overflow
Build and tag the image with creack/node:latest $ ID=$(docker build -q -t creack/node .) Add a new tag $ docker tag $ID creack/node:0.10.24....
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 Fundamentals of Docker Image Tags | Atomist Blog
Docker tags make it easy to benefit from the hard work of others by running their images directly or by creating new derived...
Read more >Understanding Docker image tags and publishing ... - ITNEXT
The <image> is the image we want the new tag to refer. We can use the image ID for this value or the...
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
Proposal:
image:tag
->{flow.name}:{timestamp}
If, in addition, we updated it with
{flow.name}:latest
as well, then users could trivially pull and test new buildsYeah I’m game for timestamp as default