Research Docker versioning techniques and value

[bhgrant8]

One option with Docker containers is to deploy and continually install from "latest", as we us travis, we can rollback via triggering a previous build.

However does it make sense to use a more defined versioning system for our images?

https://medium.com/@mccode/the-misunderstood-docker-tag-latest-af3babfd6375
https://vsupalov.com/docker-latest-tag/

Point to some concerns

some resources regarding versioning of images:

https://www.techrepublic.com/article/how-to-use-docker-tags-to-add-version-control-to-images/
https://medium.com/travis-on-docker/how-to-version-your-docker-images-1d5c577ebf54

So some questions we would like to answer:

• what are benefits of versioning docker image? what maybe detractors (ie: time/complexity/maintenance...)?
• what are strategies for implementing versioning of docker images?
• how would we implement versioning in a developer and ci/cd workflow using travis?
• does docker version tags interact with github version tags?

with this information we could decide whether to use docker version tags to integrate?