Trivy 0.51.0 rootfs scan throwing FATAL during vuln scan on root directory #6624
Replies: 3 comments 4 replies
-
Confirmed same issue on Debian 12
|
Beta Was this translation helpful? Give feedback.
-
Hi, it looks like I'm having a similar problem. It appears when I run Trivy from inside docker container, when I run Trivy locally (native binary, no container) it's fine.
I guess I can try skipping |
Beta Was this translation helpful? Give feedback.
-
I've been running into similar issues. Mostly inside of docker directories. Not necessarily when running inside of Docker, this specific log was from Trivy installed directly on an Ubuntu 22.04 vm.
Does Trivy get a list of files and then scan them after? So if a file is temporary, and the running process removes it, then Trivy errors out? Is there a way to tell Trivy that it shouldn't end the run when that happens? I mean, skipping directories is not exactly what you want to do when you are scanning for security issues... |
Beta Was this translation helpful? Give feedback.
-
Description
After Upgrading Trivy to the latest v0.51.0 version, rootfs scans appear to be crashing with the below FATAL when scanning the root directory "/"
The
lstat /proc/3471/fd/12: no such file or directory"
error always seems to be the process of the running Trivy scanThe scan works with no issues with the previous v0.50.4 version
Can workaround this issue by adding "--skip-dirs "/proc/"" argument to the scan line
Desired Behavior
The scan should work
Actual Behavior
We are seeing the below FATAL
Reproduction Steps
Target
Filesystem
Scanner
Vulnerability
Output Format
Table
Mode
Standalone
Debug Output
Operating System
CentOS7, Oracle Linux 9
Version
Checklist
trivy image --reset
Beta Was this translation helpful? Give feedback.
All reactions