Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Nitpick | 🔵 Trivial
Consider version pinning or explicitly acknowledging the trade-off.
The linter flags DL3018 for unpinned package versions. For
ca-certificates, there's a trade-off: pinning improves reproducibility but can break builds when Alpine removes older versions. Since this is a security-critical package that should stay updated anyway, the unpinned approach is defensible here.If you want to suppress the warning explicitly while keeping the current behavior, you can add an ignore directive:
Option: Suppress linter warning
+# hadolint ignore=DL3018 RUN apk add --no-cache ca-certificates && update-ca-certificatesAlternatively, pin the version if strict reproducibility is required for your environment.
📝 Committable suggestion
🧰 Tools
🪛 GitHub Check: docker-lint
[failure] 20-20:
DL3018 warning: Pin versions in apk add. Instead of
apk add <package>useapk add <package>=<version>🤖 Prompt for AI Agents