# Docker Image Tagging Suggestions

**URL:** <https://community.replicated.com/t/docker-image-tagging-suggestions/32>\
**Category:** Packaging an application\
**Created:** [March 6, 2018, 7:25pm UTC](https://community.replicated.com/t/docker-image-tagging-suggestions/32 "2018-03-06T19:25:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marc](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/marc/32/7_2.png) [@marc](https://community.replicated.com/u/marc)\
**Post date:** [March 6, 2018, 7:25pm UTC](https://community.replicated.com/t/docker-image-tagging-suggestions/32/1 "2018-03-06T19:25:59Z")

</div>

For your Replicated YAML, we highly encourage you to push images with a specific tag & avoid the  
“latest” tag. This rule can be ignored when you’re in early development stages and constantly  
updating your images. However, once you’re becoming more production ready, we suggest tagging  
images with some type of version (Replicated tags images using SHA of the GitHub commit). This is  
valuable when you have multiple release channels & want to be able to maintain a constant version  
in the stable channel, but experiment with the unstable channel.