DockerHub reduced the maximum pulls per hour, causing people can't pull all the images properly

[aldy505]

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: https://github.com/getsentry/relay/issues/4517 Craft: https://github.com/getsentry/craft/issues/591

[aldy505]

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]

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]

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.

[aldy505]

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.

[aldy505]

We've there suddenly

Project	DockerHub	GitHub Container Registry
sentry	getsentry/sentry:${VERSION}	ghcr.io/getsentry/sentry:${VERSION}
snuba	getsentry/snuba:${VERSION}	ghcr.io/getsentry/snuba:${VERSION}
symbolicator	getsentry/symbolicator:${VERSION}	ghcr.io/getsentry/symbolicator:${VERSION}
relay	getsentry/relay:${VERSION}	ghcr.io/getsentry/relay:${VERSION}
vroom	getsentry/vroom:${VERSION}	ghcr.io/getsentry/vroom:${VERSION}
taskbroker (new service)	getsentry/taskbroker:${VERSION}	ghcr.io/getsentry/taskbroker:${VERSION}

What's missing from the GHCR is that relay and symbolicator needs to release a nightly tag. Therefore self-hosted people can switch registries easily.

[aldy505]

All images are available on GHCR now.