reure1

The tool does not allow absolute paths. I am not using a container, so I'm scanning the whole system, minus some directories. [Excluding file paths](https://github.com/anchore/syft/wiki/excluding-file-paths). You can see in the...

@kzantow, when you ran your scan did you use -vv or --verbose=2? When you look at the logs you will see directories that you excluded that you don't have permissions...

I ran Syft 1.12.2 this morning and the indexer/resolver ignores --exclude also. Syft crashes at the same place. Why it crashes instead of just printing the warning, I don't know....

@kzantow, thank you for your response. I mostly agree with you. I feel that if syft didn't try to access files it was told to ignore symlink or not, the...

I will see if we can come up with something. We may just have to use a different SBOM tool.

@kzantow btw there is a symlink for /etc/grub2.cfg and ../boot/grub2.cfg What are your permissions for /boot and /boot/grub2? On this system: /boot is 555 /boot/grub2 is 700 Both owned by...

I started looking at the code. This will give me a chance to learn a little Go. lstat is only on one place. So I will start there. ``` syft/internal/fileresolver/directory_indexer.go:218...

I had to work on something else for a few days. I'm glad to see someone else had the issue and could easily reproduce it.

@kzantow, I came up with a quick fix. In syft/internal/fileresolver/directory_indexer.go I changed line 91 from: ```go return fmt.Errorf("unable to index filesystem path=%q: %w, currentPath, err) ``` to: ```go log.WithFields("path", currentPath).Warn("unable...