anchore / anchore/syft

Can Syft scan a running container, in case it has changed from the image it started from?

Open
#4,158 18 comments 0 reactions 0 assignees View on GitHub
enhancement needs-investigation
Dominant language
Go
Stars
9.6k
Forks
962
Avg merge
23h 27m
Merged PRs (30d)
48

Description

**What happened**: Running syft 'package' , I get a SBOM, but none of the package versions match what is in /var/lib/dpkg/status

**What you expected to happen**: I expect them to match..
Example adduser - syft says 3.134, but status says 3.118

**Steps to reproduce the issue**: Running the binary

**Anything else we need to know?**:

**Environment**:
- Output of `syft version`: 1.18.1
- OS (e.g: `cat /etc/os-release` or similar): Rocky 8

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported result with the Syft binary on a running container, comparing package versions against /var/lib/dpkg/status. The work is complete when scanning the running container reflects its current package state rather than only the image it started from.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.