-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot scan AMI on AWS with v0.4.8.1 #5821
Comments
@nikpivkin @masahiro331 It's still does not work with v0.48.2. One can see this error message when switching from 0.48.0 to 0.48.2, with same conf & env, just changing image tag: 2024-01-11T13:27:28.581Z INFO Snapshot snap-0793dc1b3b75c0cac found
2024-01-11T13:27:28.582Z FATAL vm scan error: scan error: scan failed: failed analysis: EBS open error: EBS error: not found, ResolveEndpointV2
2024-01-11T13:27:30.503Z INFO Vulnerability scanning is enabled
2024-01-11T13:27:30.503Z INFO Misconfiguration scanning is enabled
2024-01-11T13:27:31.289Z INFO Snapshot snap-0e788653fa93a9d4e found
2024-01-11T13:27:31.290Z FATAL vm scan error: scan error: scan failed: failed analysis: EBS open error: EBS error: not found, ResolveEndpointV2
2024-01-11T13:27:33.166Z INFO Vulnerability scanning is enabled
2024-01-11T13:27:33.166Z INFO Misconfiguration scanning is enabled
2024-01-11T13:27:33.830Z INFO Snapshot snap-0f8a3647c96941cae found
2024-01-11T13:27:33.830Z FATAL vm scan error: scan error: scan failed: failed analysis: EBS open error: EBS error: not found, ResolveEndpointV2 |
@masahiro331 I've opened a PR, could you take a look? |
#5822 did not fix the issue - is there an update on this?? - trying to follow the multiple threads and there's not really an answer on this one yet that I can see thanks |
@tburow Fixed in #5934. You can try canary builds. |
is there going to be a patch release or do we need to wait for .49? if .49 when will that be? - Thanks again |
v0.49.0 will include it. |
Discussed in #5807
Originally posted by mloiseleur December 19, 2023
Description
Same scan command, that did work with v0.48.0 do not work with v0.48.1.
It seems it encounter this specific issue: aws/aws-sdk-go-v2#2370 , when an AWS go mod dependency has been updated but not the others.
Desired Behavior
Actual Behavior
Reproduction Steps
Note: same exact command works perfectly fine with v0.48.0
Target
Virtual Machine Image
Scanner
Vulnerability
Output Format
None
Mode
None
Debug Output
Operating System
Linux AMD64
Version
Checklist
trivy image --reset
The text was updated successfully, but these errors were encountered: