I am aware that syft can get exclusions in the configuration. My question is syft has directories which he doesn’t index \ scan (without getting it from the configuration)
Thanks.
I am aware that syft can get exclusions in the configuration. My question is syft has directories which he doesn’t index \ scan (without getting it from the configuration)
Thanks.
We do have certain parts of the filetree for directory scans that we ignore, which is based on the path and filesystem type for the mountpoint syft/syft/internal/fileresolver/path_skipper.go at d7005d7d8ca6d05f594f7bc1a140ae1e85bc0328 · anchore/syft · GitHub
Specifically:
/proc
if it is of filesytem types procfs
or proc
/sys
if it is of filesystem type sysfs
or tmpfs
/dev
if it is of filesystem types devfs
, devtmpfs
, udev
, or tmpfs
/run
, /var/run
, /var/lock
if it’s of filesystem type tmpfs
This prevents from scanning directories that tend to not have software and can be problematic to scan (large symlink loops, odd device files, etc).
I don’t think there are other kinds of exclusions made from an indexer-perspective, and this is only applied to directory scans, not image scans.