4 ms·
As long as the Dockerfile is released alongside, this should not be an issue. I don't see any valid reason why anyone would upload and share a public docker im
by Legogris 6y ago
As long as the Dockerfile is released alongside, this should not be an issue.
I don't see any valid reason why anyone would upload and share a public docker image but not its Dockerfile and therefore do not pull anything from Dockerhub that doesn't also have the Dockerfile on the Dockerhub page.
- Bedon292 6y agoWhat about when the image that it is based on goes out of date and is pruned too?
- Legogris 6y agoThis is part of why I tend to only use images that only build from a small set of well-established base images like scratch, alpine, debian and occasionally ubuntu. Those base images can also be handled in the same way. For any exception, you can always do the same. A bonus to this is that you no longer have the risks of systems breaking because of Dockerhub or quay.io (which I haven't seen mentioned here yet, btw) being offline.
- jacques_chester 6y agoDockerfiles are not guaranteed to be reproducible. They can run arbitrary logic which can have arbitrary side-effects. A classic is `wget https://example.com/some-dependency/download/latest.tgz` https://example.com/some-dependency/download/latest.tgz`.