add OCI stage detection to Dockerfile signal#9
Merged
Conversation
Detects the OS package manager and distro from each FROM image using a three-pass algorithm (standalone distros → tag keyword scan → known runtime defaults), and extracts packages installed via RUN commands in every stage. Surfaces as `oci_stages: Vec<OciStage>` on `Service`. Each OciStage carries the stage name (FROM ... AS name), detected manager (apt/apk/yum/dnf), distro codename/version from the tag (e.g. "noble", "bookworm", "3.19"), and raw package names as written. All stages are collected, not just the last, so build-time and runtime deps are both visible and labeled. `system_deps` (language-signal inferences, always apt-canonical) and `oci_stages` (Dockerfile declarations, raw) are intentionally separate. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
Detects the OS package manager and distro from each FROM image using a
three-pass algorithm (standalone distros → tag keyword scan → known
runtime defaults), and extracts packages installed via RUN commands in
every stage. Surfaces as
oci_stages: Vec<OciStage>onService.Each OciStage carries the stage name (FROM ... AS name), detected
manager (apt/apk/yum/dnf), distro codename/version from the tag (e.g.
"noble", "bookworm", "3.19"), and raw package names as written. All
stages are collected, not just the last, so build-time and runtime deps
are both visible and labeled.
system_deps(language-signal inferences, always apt-canonical) andoci_stages(Dockerfile declarations, raw) are intentionally separate.