'$dc pull relay' exited with status 1

[songlongkuan]

Self-Hosted Version

25.5.1

CPU Architecture

x86_64

Docker Version

28.1.1

Docker Compose Version

2.35.1

Machine Specification

• [x] My system meets the minimum system requirements of Sentry

Steps to Reproduce

ubuntu system ,run install.sh fail:

▶ Creating volumes for persistent storage ... Created sentry-clickhouse. Created sentry-data. Created sentry-kafka. Created sentry-postgres. Created sentry-redis. Created sentry-symbolicator.

▶ Ensuring files from examples ... sentry/sentry.conf.py already exists, skipped creation. sentry/config.yml already exists, skipped creation. symbolicator/config.yml already exists, skipped creation.

▶ Checking memcached backend ... PyMemcacheCache found in sentry/sentry.conf.py, gonna assume you're good.

▶ Ensuring Relay credentials ... relay/config.yml already exists, skipped creation. relay Pulling relay Error Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Error in install/ensure-relay-credentials.sh:27. '$dc pull relay' exited with status 1 -> ./install.sh:main:35 --> install/ensure-relay-credentials.sh:source:27

Cleaning up...

but,curl https://registry-1.docker.io is success: root@i-xxxxxxxxxx:/opt/sentry/self-hosted-25.5.1# curl https://registry-1.docker.io/v2 Moved Permanently.

Expected Result

install success

Actual Result

▶ Parsing command line ...

▶ Detecting Docker platform Detected Docker platform is linux/amd64

▶ Initializing Docker Compose ... docker compose --ansi never --env-file .env run --pull=never --rm

▶ Setting up error handling ... #0 building with "default" instance using docker driver

#1 [internal] load build definition from Dockerfile #1 transferring dockerfile: 292B done #1 DONE 0.0s

#2 [internal] load metadata for docker.io/library/debian:bookworm-slim #2 DONE 0.2s

#3 [internal] load .dockerignore #3 transferring context: 2B done #3 DONE 0.0s

#4 [1/2] FROM docker.io/library/debian:bookworm-slim@sha256:302ff7cde82ce20eb79ee3d8685a9e3e3a683cae5f86851e821153223cca7def #4 DONE 0.0s

#5 [2/2] RUN set -x && apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends jq && apt-get clean && rm -rf /var/lib/apt/lists/* #5 CACHED

#6 exporting to image #6 exporting layers done #6 writing image sha256:d6a2e073d55d53455fbebbeeffe963d5995749b98a6885d9c84d8b35781a54c5 done #6 naming to docker.io/library/sentry-self-hosted-jq-local done #6 DONE 0.0s

Hey, so ... we would love to automatically find out about issues with your Sentry instance so that we can improve the product. Turns out there is an app for that, called Sentry. Would you be willing to let us automatically send data about your instance upstream to Sentry for development and debugging purposes?

y / yes / 1 n / no / 0

(Btw, we send this to our own self-hosted Sentry instance, not to Sentry SaaS, so that we can be in this together.)

Here's the info we may collect:

• OS username
• IP address
• install log
• runtime errors
• performance data

Thirty (30) day retention. No marketing. Privacy policy at sentry.io/privacy.

y or n? Understood. To avoid this prompt in the future, use one of these flags:

--report-self-hosted-issues --no-report-self-hosted-issues

or set the REPORT_SELF_HOSTED_ISSUES environment variable:

REPORT_SELF_HOSTED_ISSUES=1 to send data REPORT_SELF_HOSTED_ISSUES=0 to not send data

▶ Checking for latest commit ... skipped

▶ Checking minimum requirements ... Found Docker version 28.1.1 Found Docker Compose version 2.35.1

▶ Upgrading Clickhouse ...

▶ Turning things off ...

▶ Creating volumes for persistent storage ... Created sentry-clickhouse. Created sentry-data. Created sentry-kafka. Created sentry-postgres. Created sentry-redis. Created sentry-symbolicator.

▶ Ensuring files from examples ... sentry/sentry.conf.py already exists, skipped creation. sentry/config.yml already exists, skipped creation. symbolicator/config.yml already exists, skipped creation.

▶ Checking memcached backend ... PyMemcacheCache found in sentry/sentry.conf.py, gonna assume you're good.

▶ Ensuring Relay credentials ... relay/config.yml already exists, skipped creation. relay Pulling relay Error Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Error in install/ensure-relay-credentials.sh:27. '$dc pull relay' exited with status 1 -> ./install.sh:main:35 --> install/ensure-relay-credentials.sh:source:27

Cleaning up...

Event ID

No response

[aldy505]

relay Error Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Error response from daemon: Get "https://registry-1.docker.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

This is your network issue speaking. Try to check your bandwidth/connection stability.

[getsantry[bot]]

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 🥀