-
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
ECR repository behind friendly URL throws errors #6885
Comments
Alternatively is there anything in the headers that are returned from the rejection that we can detect/parse and retry with 1000 instead of 10000 ? |
@jonathanmorley Do you know any public ecr docker repo we can test against ? |
Idea: check for amazon headers in getAuthHeaders, eg: |
I don't know of any public ECR docker repo we could use for this, but I can say that our proxy that fronts ECR does not respond with any headers identifying it as fronting AWS or the limit it supports |
We could recognise the specific error message that ECR throws:
Headers:
And handle it by dropping the limit down |
There's a typo in the PR title: Change |
Related: #11322 (might be the solution for this issue) |
We are also blocked from using the docker datasource because of this issue. The related issue suggests that this is a policy issue, which is not the case for us. Ideally, like this issue suggests, we would be able to somehow configure which Looking forward to updates on this. |
PRs welcome. It needs someone using this setup of ECR to fix and verify it. |
🎉 This issue has been resolved in version 31.45.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This is the same as #3800, but with the addition of friendly URLs in front of ECR.
Proposal
Add a config value to be able to manually drop the docker limits value from
renovate/lib/datasource/docker/index.js
Line 276 in 6de255e
The text was updated successfully, but these errors were encountered: