3 ms·
You are mixing build time reproduction with run time ones. Docker images (not files) help with the run time consistency . Docker (files) barely scratch the su
by manquer 1y ago
You are mixing build time reproduction with run time ones.
Docker images (not files) help with the run time consistency .
Docker (files) barely scratch the surface of build reproducibility. Most applications depend on the distribution package manager ( apt, apk etc) and language package manager (npm, cargo, etc), both sets of them have various challenges in consistent dependency resolution.
In addition build steps might have ordering challenges RPC calls to remote services no longer running and so on.
Anyone trying to to build a docker image from 10 years back experiences this problem
- wink 1y agoYou're right in the absolute form, but I've yet to see a Dockerfile where (with a little thinking and elbow grease) I couldn't "easily" port it or update it, even after years. It's basically the best and easiest "I am documenting how it works now" thing without any arcane "works on my machine" quirks I have yet found. So I'm still agreeing here that it's a very good approximation of this idea. Real reproducability is miles better, but usually cannot be formulated in a ~20 line single file "recipe". (and before anyone mentions Nix.. no, there's so much inherent complexity involved, that doesn't count like "apt-get install docker && docker build ."