Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid usage of "latest" or git-master dependencies #15

Open
squix78 opened this issue May 9, 2017 · 0 comments
Open

Avoid usage of "latest" or git-master dependencies #15

squix78 opened this issue May 9, 2017 · 0 comments

Comments

@squix78
Copy link
Contributor

squix78 commented May 9, 2017

In the docker file we use "FROM resin/rpi-raspbian" which uses the latest release of the rpi-raspbian image. This can introduce instability when the parent image has changed in the meantime. Similarly cloning the master version of a git-repo in the Dockerfile can lead to inconsistent behavior if no tag has been used. If the image is built at different points in time the resulting image can look different with every build.

This can be compared to a maven release which should not have dependencies to any unreleased version of other libraries.

In addition the image on dockerhub should get tagged not just with "latest" but with versions

Thanks to @marschall for the input.

Here some more reading about the topic:
https://medium.com/@mccode/the-misunderstood-docker-tag-latest-af3babfd6375
http://blog.benhall.me.uk/2015/01/dockerfile-latest-tag-anti-pattern/
http://container-solutions.com/docker-latest-confusion/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant