-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
DockerHub reduced the maximum pulls per hour, causing people can't pull all the images properly #3593
Comments
This is not the 1st April yet, but I got this, don't know why. Probably this will be the same message on 1st April:
I found out a bit later: I got rate limited by DockerHub, since the existing limit was per IPv4 block and the onprem CI runner on my company that was pulling some Docker images, so there we go |
Heya @bc-sentry @asottile-sentry @hubertdeng123, I don't know people other than the devinfra team. But can you guys help escalate this internally please? Thanks! |
I got this error trying to restart the service with new version: failed to solve: sentry-self-hosted-local: failed to resolve source metadata for docker.io/library/sentry-self-hosted-local:latest: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed I authenticated docker so most likely I have 100 rate limit but this seems something else. |
@ganeshkrishnan1 that's pretty common and caused by something else. Usually it's because your Docker proxy settings, or you didn't run install.sh for upgrades. |
Similar work with these PRs: - getsentry/relay#4532 - getsentry/symbolicator#1635 While also trying to provide a solution (or at least an alternative) for this issue: getsentry/self-hosted#3593 ### Legal Boilerplate Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
Problem Statement
Discord thread: https://discord.com/channels/621778831602221064/1342532967406501908
DockerHub link to the problem: https://docs.docker.com/docker-hub/usage/
Solution Brainstorm
What if we publish to both DockerHub (for compatiblity reasons) and to GitHub Container Registry (which is free for public repositories, and have been done by some repositories: Relay, Symbolicator)
Track other stuffs here:
Relay: getsentry/relay#4517
Craft: getsentry/craft#591
The text was updated successfully, but these errors were encountered: