In a CI/CD pipeline, why might "docker build" results vary between runs even with an identical Dockerfile and source code, and what techniques help ensure reproducibility?
Correct! Well done.
Incorrect.
The correct answer is B) Non-determinism can arise from unpinned image tags or package versions resolving to newer releases over time, embedded timestamps, or network-dependent steps; pinning images by digest and locking dependency versions improves reproducibility
Correct Answer
Non-determinism can arise from unpinned image tags or package versions resolving to newer releases over time, embedded timestamps, or network-dependent steps; pinning images by digest and locking dependency versions improves reproducibility
Mutable references (tags, "latest" dependency versions) and non-deterministic build steps (timestamps, network calls returning different data over time) can cause the same Dockerfile to produce different images on different days; pinning versions/digests and using lockfiles reduces this variability.