fix: set GH_TOKEN in build workflow and ignore Trivy DS-0002#30
Merged
Conversation
The build workflow fails because `gh release download` requires GH_TOKEN to be set in GitHub Actions, even for public repos. The security scan fails on DS-0002 (missing non-root USER in Dockerfiles) which is a false positive — these are microVM rootfs images where isolation comes from the VM boundary, not user namespaces. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
rdimitrov
approved these changes
Mar 17, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
task buildcallsgh release downloadto fetch go-microvm runtime/firmware artifacts. TheghCLI refuses to run in GitHub Actions withoutGH_TOKENset — even for public repos. AddedGH_TOKEN: ${{ github.token }}to the Build step.USERin Dockerfiles) on all images. These are microVM rootfs images, not traditional containers — isolation comes from the VM boundary (libkrun), not Linux user namespaces. Added.trivyignoreto suppress this false positive.Test plan
🤖 Generated with Claude Code