This repository was archived by the owner on Jul 17, 2026. It is now read-only.
Enable Trivy container CVE scan (ENG-314)#427
Open
dblane-digicatapult wants to merge 2 commits into
Open
Conversation
Sets scan_container: true on the build-docker call(s) so the built amd64 image is scanned with Trivy and the build fails on CRITICAL findings. ENG-314
dblane-digicatapult
added
the
v:patch
ehaldane-digicatapult
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Linked tickets
ENG-314
High level description
Enables the Trivy container CVE scan by setting
scan_container: trueon the sharedbuild-dockercall (test and release). The builtlinux/amd64image is scanned with a digest-pinned Trivy; the build fails on CRITICAL findings and uploads a JSON report artifact (no GHAS upload). Scan runs in an isolated least-privilege job.PR Type
Operational impact
CI-only. Adds an isolated scan job to the docker build on PR and release. Fails the build on CRITICAL image CVEs.