Project setup > failed to solve: sentry-self-hosted-local: pull access denied

[joechron]

Self-Hosted Version

21.7.0

CPU Architecture

x86_64

Docker Version

20.10.24

Docker Compose Version

2.17.2

Steps to Reproduce

1. Clone repo to local directory
2. run ./install.sh --skip-user-creation
3. Receive error:

#2 [internal] load metadata for docker.io/library/sentry-self-hosted-local:latest
#2 ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
------
 > [internal] load metadata for docker.io/library/sentry-self-hosted-local:latest:
------
failed to solve: sentry-self-hosted-local: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Error in install/build-docker-images.sh:8.
'$dcb --force-rm "$service"' exited with status 17
-> ./install.sh:main:29
--> install/build-docker-images.sh:source:8

Expected Result

I expect to be able to get sentry running locally by following the readme steps.

Actual Result

#2 [internal] load metadata for docker.io/library/sentry-self-hosted-local:latest
#2 ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
------
 > [internal] load metadata for docker.io/library/sentry-self-hosted-local:latest:
------
failed to solve: sentry-self-hosted-local: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Error in install/build-docker-images.sh:8.
'$dcb --force-rm "$service"' exited with status 17
-> ./install.sh:main:29
--> install/build-docker-images.sh:source:8

Event ID

No response

[azaslavsky]

Authorization issues like this are almost always caused by local network, firewall, or security configurations. This test runs okay on our CI, which implies that barring any interferences, we're able to pull with no problems in the general case.

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[xunjianxiang]

I have the same issue~~
don't know how to fix it

[itDjango]

I also encountered the same problem and tried many methods, but still couldn't solve it

[azaslavsky]

Curious if the solution this user tried will help in your case: #2563.

[joechron]

Curious if the solution this user tried will help in your case: #2563.

@azaslavsky No, it did not. That is a different issue.

[itDjango]

Curious if the solution this user tried will help in your case: #2563.

I hope someone has solved this problem and I can learn from it. Thank you

[azaslavsky]

So another issue that could cause this is an OOM - either docker ran out of allocated memory, or your VM that's hosting it did. Not guaranteed that this is the root cause, but this is often what happens when you get an unexpected EOF while pulling down the (very large) dependencies. Can you monitor memory while running the script?

[pquerner]

$ docker compose build
[+] Building 0.2s (11/19)                                                                                                                                docker:default
 => [vroom-cleanup internal] load build definition from Dockerfile                                                                                                 0.1s
 => => transferring dockerfile: 469B                                                                                                                               0.0s
 => [symbolicator-cleanup internal] load build definition from Dockerfile                                                                                          0.0s
 => => transferring dockerfile: 469B                                                                                                                               0.0s
 => [clickhouse internal] load build definition from Dockerfile                                                                                                    0.0s
 => => transferring dockerfile: 71B                                                                                                                                0.0s
 => [symbolicator-cleanup internal] load metadata for docker.io/getsentry/symbolicator:24.4.2                                                                      0.0s
 => [vroom-cleanup internal] load metadata for docker.io/getsentry/vroom:24.4.2                                                                                    0.0s
 => [vroom-cleanup internal] load .dockerignore                                                                                                                    0.1s
 => => transferring context: 2B                                                                                                                                    0.0s
 => [symbolicator-cleanup internal] load .dockerignore                                                                                                             0.1s
 => => transferring context: 2B                                                                                                                                    0.0s
 => [vroom-cleanup internal] load build context                                                                                                                    0.0s
 => => transferring context: 35B                                                                                                                                   0.0s
 => [vroom-cleanup 1/5] FROM docker.io/getsentry/vroom:24.4.2                                                                                                      0.0s
 => CANCELED [symbolicator-cleanup internal] load build context                                                                                                    0.0s
 => => transferring context:                                                                                                                                       0.0s
 => [symbolicator-cleanup 1/5] FROM docker.io/getsentry/symbolicator:24.4.2                                                                                        0.0s
failed to solve: base name (${BASE_IMAGE}) should not be blank

$ docker compose --verbose build
TRAC[0000] Docker Desktop integration not enabled
DEBU[0000] using default config store "/root/.docker/buildx"
[+] Building 0.1s (4/4) FINISHED                                                                                                                         docker:default
 => [clickhouse internal] load build definition from Dockerfile                                                                                                    0.0s
 => => transferring dockerfile: 71B                                                                                                                                0.0s
 => [vroom-cleanup internal] load build definition from Dockerfile                                                                                                 0.0s
 => => transferring dockerfile: 469B                                                                                                                               0.0s
 => [vroom-cleanup internal] load metadata for docker.io/getsentry/vroom:24.4.2                                                                                    0.0s
 => CANCELED [vroom-cleanup internal] load .dockerignore                                                                                                           0.0s
DEBU[0000] using default config store "/root/.docker/buildx"
DEBU[0000] using default config store "/root/.docker/buildx"
DEBU[0000] using default config store "/root/.docker/buildx"
DEBU[0000] serving grpc connection
DEBU[0000] stopping session                              span="load buildkit capabilities"
DEBU[0000] serving grpc connection
DEBU[0000] stopping session                              span="load buildkit capabilities"
DEBU[0000] serving grpc connection
DEBU[0000] stopping session                              span="load buildkit capabilities"
DEBU[0000] serving grpc connection
DEBU[0000] stopping session
DEBU[0000] serving grpc connection
DEBU[0000] stopping session
DEBU[0000] serving grpc connection
DEBU[0000] stopping session
DEBU[0000] serving grpc connection
DEBU[0000] serving grpc connection
DEBU[0000] stopping session
DEBU[0000] stopping session
failed to solve: base name (${BASE_IMAGE}) should not be blank

[azaslavsky]

Hmmm, yeah, that makes sense. I'm really not sure what could be happening - we're unable to replicate this on any of our local instances.

[pquerner]

Okay, thanks for looking at it anyways. I'll try to replicate on other hardware. (Just wierd that its happening all of the sudden. Maybe some wierd docker update...)

[pquerner]

I deleted my old folder (no git changes) and git clone a fresh one. Same directory name. Then install.sh, then docker compose up and now its working..

not sure why.. git detected no changes. mh..

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀