contrib: ignore cache when rebuilding docker builder images
What the developer wrote
Authored by Alex Myers
contrib: ignore cache when rebuilding docker builder images
This caused issues when dependencies were updated do to cached
images continuing to be used.
Changelog-None
What changed, and why it matters
This change adds a Docker command-line flag that forces builder images to be rebuilt from scratch instead of reusing cached layers. It is a build-hygiene fix to avoid stale cached images after dependency updates. There is no security vulnerability here.
No security action needed. Treat as a normal build-script maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies contrib/cl-repro.sh to pass –no-cache to docker build when building reproducible-builder images for Ubuntu distributions. This prevents Docker from using previously cached layers, ensuring dependency updates in the Dockerfile are actually reflected. The change is purely operational/build-process related and does not alter runtime code, network exposure, or cryptographic handling.
Changed components
contrib/cl-repro.shInspect captured patch +1 / −1
diff --git a/contrib/cl-repro.sh b/contrib/cl-repro.sh
index 87e61412..1911328d 100755
--- a/contrib/cl-repro.sh
+++ b/contrib/cl-repro.sh
@@ -23,5 +23,5 @@ for v in focal jammy noble; do
sudo docker run ubuntu:$v cat /etc/lsb-release
echo "Building CL repro $v:"
# shellcheck disable=SC2024
- sudo docker build -t cl-repro-$v - < "$LIGHTNING_DIR"/contrib/reprobuild/Dockerfile.$v
+ sudo docker build --no-cache -t cl-repro-$v - < "$LIGHTNING_DIR"/contrib/reprobuild/Dockerfile.$v
done
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.