(no title)
jhanoncomm | 1 year ago
And that all relies on discipline. Just like using a dynamically typed programming language can in theory have no type errors at run time, if you are careful enough.
jhanoncomm | 1 year ago
And that all relies on discipline. Just like using a dynamically typed programming language can in theory have no type errors at run time, if you are careful enough.
yjftsjthsd-h|1 year ago
And then there's the Dockerfiles that just `RUN git clone repo.git` and run with whatever happened to be in the latest commit at the moment...
janjongboom|1 year ago
nullify88|1 year ago
cpuguy83|1 year ago
MadnessASAP|1 year ago
Dockerfiles being at their core a set of instructions for producing a container image could of course be used to make a reproducible image. Although you'd have to be painfully verbose to ensure that you got the exact same output. You would actually likely need 2 files, the first being the build environment that the second actually get built in.
Or you could use Nix that is actually intended to do this and provides the necessary framework for reproducibility.
inopinatus|1 year ago
[1] https://en.wikipedia.org/wiki/Impact_driver#Manual_impact_dr...