You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On certain entreprise network, we can get easily the API rate limit exceeded github problem.
The following extensions will not work
kind
main ↪️ [kind] Error: API rate limit exceeded for 91.103.43.254. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)
compose
nothing will happen when clicking on the compose bottom menu item.
Operating system
Windows 10
Installation Method
Installer from website/GitHub releases
Version
1.4.0
Steps to reproduce
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi @axel7083, in Settings > Registries you can provide a login to Docker Hub. Is the main issue that it's not working / that the auth isn't being applied in some scenarios, that you couldn't find it, that there wasn't a proper error message (esp. compose), or it didn't direct you where to fix? Or all of the above? :) I just want to make sure we're tracking the correct problem, and if there are multiple we should probably split this up/open another issue.
There are no message shown to the user either for kind and compose, the only message I was able to find was in the Troubleshooting logs component, showing the error in red main ↪️ [kind] Error: API rate limit exceeded for XXXXXXXX. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)
Bug description
On certain entreprise network, we can get easily the
API rate limit exceeded
github problem.The following extensions will not work
Operating system
Windows 10
Installation Method
Installer from website/GitHub releases
Version
1.4.0
Steps to reproduce
No response
Relevant log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: