Skip to content
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

Open
aldy505 opened this issue Feb 28, 2025 · 4 comments
Assignees

Comments

@aldy505
Copy link
Collaborator

aldy505 commented Feb 28, 2025

Problem Statement

Discord thread: https://discord.com/channels/621778831602221064/1342532967406501908

Image

DockerHub link to the problem: https://docs.docker.com/docker-hub/usage/

Image

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

@aldy505
Copy link
Collaborator Author

aldy505 commented Feb 28, 2025

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:

 kafka Pulling
 redis Pulling
 memcached Pulling
 vroom-cleanup Pulling
 uptime-checker Pulling
 clickhouse Pulling
 relay Pulling
 nginx Pulling
 postgres Pulling
 symbolicator Pulling
 symbolicator-cleanup Pulling
 smtp Pulling
 vroom Pulling
 sentry-cleanup Pulling
 cron Pulling
 snuba-profiling-functions-consumer Pulled
 nginx Pulled
 symbolicator Pulled
 vroom Pulled
 smtp Pulled
 postgres Pulled
 memcached Pulled
 relay Pulled
 redis Pulled

WARNING: Some service image(s) must be built from source by running:
    docker compose build cron vroom-cleanup symbolicator-cleanup uptime-checker clickhouse sentry-cleanup

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

@aldy505
Copy link
Collaborator Author

aldy505 commented Feb 28, 2025

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!

@ganeshkrishnan1
Copy link

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.
I cant even go back to old version now.

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Mar 10, 2025
@aldy505
Copy link
Collaborator Author

aldy505 commented Mar 10, 2025

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.
I cant even go back to old version now.

@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.

untitaker pushed a commit to getsentry/snuba that referenced this issue Mar 25, 2025
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.
@aldy505 aldy505 self-assigned this Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Status: No status
Development

No branches or pull requests

2 participants