What the developer wrote
Authored by will
ci: fix annoying docker warning
Docker currently warns that we are missing a default value.
Set this to scratch which will error if an appropriate image tag is not
passed in to silence the warning.
What changed, and why it matters
This is a minor CI (Continuous Integration) configuration change. It adds a default value of 'scratch' to a Docker build argument to silence a harmless warning from Docker. There is no security issue here.
No security action needed. This is a routine CI quality-of-life fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies ci/test_imagefile to set a default value (scratch) for the ARG CI_IMAGE_NAME_TAG. Previously, Docker emitted a warning because the ARG had no default. The default ‘scratch’ is intentionally invalid as a runtime image and will cause a build failure if no proper CI_IMAGE_NAME_TAG is passed in, ensuring the warning is silenced without changing actual build behavior when the argument is supplied.
Changed components
ci/test_imagefileInspect captured patch +2 / −1
diff --git a/ci/test_imagefile b/ci/test_imagefile
index 224141b1..f9cf3187 100644
--- a/ci/test_imagefile
+++ b/ci/test_imagefile
@@ -4,7 +4,8 @@
# See ci/README.md for usage.
-ARG CI_IMAGE_NAME_TAG
+# We never want scratch, but default arg silences a Warning
+ARG CI_IMAGE_NAME_TAG=scratch
FROM ${CI_IMAGE_NAME_TAG}
ARG FILE_ENV
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.