Install script fails at relay credentials #3908
Description
Self-Hosted Version
25.8.0
CPU Architecture
x86_64
Docker Version
27.3.1
Docker Compose Version
2.33.1
Machine Specification
- My system meets the minimum system requirements of Sentry
Steps to Reproduce
- Using fresh installation of Photon OS 5
- git clone https://github.com/getsentry/self-hosted
- cd self-hosted
- git checkout 25.8.0
- ./install.sh
Expected Result
The installation should run without any issues.
Actual Result
▶ Parsing command line ...
▶ Detecting container engine ...
Detected container engine: docker
▶ Detecting Docker platform
Detected Docker platform is linux/amd64
▶ Initializing Docker|Podman Compose ...
docker compose --ansi never --env-file .env run --pull=never --rm
▶ Setting up error handling ...
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/buildx/
Sending build context to Docker daemon 2.048kB
Step 1/4 : FROM debian:bookworm-slim
---> f813b63f015b
Step 2/4 : LABEL MAINTAINER="oss@sentry.io"
---> Using cache
---> 16ec96fb997c
Step 3/4 : 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/*
---> Using cache
---> 82d6d7486388
Step 4/4 : ENTRYPOINT ["jq"]
---> Using cache
---> 15fad24cc1c7
Successfully built 15fad24cc1c7
Successfully tagged sentry-self-hosted-jq-local:latest
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? y
Thank you. 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
latest: Pulling from getsentry/sentry-cli
Digest: sha256:52c5cea7ea93e031cfa0fabd0d808704a8b44c871ab7120607618ed8c8d35471
Status: Image is up to date for getsentry/sentry-cli:latest
docker.io/getsentry/sentry-cli:latest
▶ Checking for latest commit ...
skipped
▶ Checking minimum requirements ...
Found docker version 27.3.1
Found docker Compose version 2.33.1
▶ Upgrading Clickhouse ...
▶ Turning things off ...
Container sentry-self-hosted-relay-1 Stopping
Container sentry-self-hosted-relay-1 Stopped
Container sentry-self-hosted-relay-1 Removing
Container sentry-self-hosted-relay-1 Removed
Network sentry-self-hosted_default Removing
Network sentry-self-hosted_default Removed
▶ 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 ...
Creating sentry/sentry.conf.py ...
Creating sentry/config.yml ...
Creating symbolicator/config.yml ...
▶ Checking memcached backend ...
PyMemcacheCache found in sentry/sentry.conf.py, gonna assume you're good.
▶ Ensuring Relay credentials ...
Creating relay/config.yml ...
relay Pulling
relay Pulled
Network sentry-self-hosted_default Creating
Network sentry-self-hosted_default Created
2025-08-28T06:57:14.976509Z INFO relay_config::config: generating new relay credentials
2025-08-28T06:57:15.571942Z ERROR relay_log::utils: error=no stored credentials
exit status 1
Failed to create relay credentials in relay/credentials.json.
--- credentials.json v ---------------------------------------
{"secret_key":"its-a-secret","public_key":"qrbb_XG0iRd0Q99nAZ_fchohDE0tOBmRuxxP_pbisTw","id":"5c1d45b5-44af-4e95-9898-f5b2dde4d701"}
--- credentials.json ^ ---------------------------------------
The file exists in the relay folder. Running manually docker compose run --rm --no-deps -T relay credentials show returns the same error.
Event ID
No response