{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 聊天终结者 的问题《do I need to manually tag “latest” when pushing to》','https://www.manongdao.com/q-1317857.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Suppose I have an image me/mystuff:v0.0.1
I find if I push it to the repository:
docker push me/mystuff:v0.0.1
latest is not created, and on a pull from another machine it will complain, e.g.
ssh me@faraway
(faraway) $ docker run -it me/mystuff /bin/bash
will result in a not found error for me/mystuff:latest
I can add the latest tag and push explicitly to the public repository:
docker login me
docker tag me/mystuff:v0.0.1 me/mystuff:latest
docker push me/mystuff:latest
and then from another machine:
docker pull me/mystuff
will work because latest exists.
I am also finding that once latest exists, it does not auto update when a new numbered version is pushed.
Can I somehow eliminate this step of manually tagging latest and have latest automatically point to the latest numbered version?
Or is it there for a reason, like allowing the separation of development versions (tagged with a vN.N.N only) from the production version (tagged latest)?
The latest is just the default value of the tag if none is specified. If you push a tagged image it does not replace the current image tagged with latest.