Version 0.66.0 not authorized with AWS #9429
Replies: 7 comments 21 replies
-
|
This might be related #9430 |
Beta Was this translation helpful? Give feedback.
-
|
We use aws ECR pull through caches in our environment for performance reasons (less bandwidth to internet, less latency, less requests made to public repos) for trivy and the db and java db. In 0.65.0 and earlier, our authenticated environment is able to pull all 3 images. In 0.66.0, now that #9322 has been merged, this now fails. To reproduce, Run trivy, using GitLab with a snippet like the following, to an authenticated AWS ECR repo. Authentication works something like this somewhere in the pipeline: With 0.65.0 this will work! With 0.66.0 this fails with: If we update the script to install docker and the aws-cli ( |
Beta Was this translation helpful? Give feedback.
-
|
@jscancella @chriskellyrelay Thanks for your information and help! |
Beta Was this translation helpful? Give feedback.
-
|
created #9437 |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
@chriskellyrelay @jscancella @eldondevat I tried to replicate it hard, but no luck. Could you share more details to help us reproduce the issue? Please feel free to mask any sensitive information, such as account numbers or credentials. You don’t have to answer all of the questions below; any additional details you can provide would be greatly appreciated.
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Description
0.65.0 works fine, but when using 0.66.0 I get this error

Desired Behavior
It to continue to work and not give authorization errors
Actual Behavior
Reproduction Steps
Target
Container Image
Scanner
None
Output Format
None
Mode
None
Debug Output
I don't have that abilityOperating System
amazon linux
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions