/etc/sentry/entrypoint.sh: no such file or directory

[erycson]

Self-Hosted Version

25.6.2

CPU Architecture

x86_64

Docker Version

20.10.24

Docker Compose Version

2.38.2

Machine Specification

• My system meets the minimum system requirements of Sentry

Steps to Reproduce

mkdir /etc/sentry
git clone --branch 25.6.2 --depth 1 https://github.com/getsentry/self-hosted.git /etc/sentry
chmod -R 777 /etc/sentry
cd /etc/sentry
DEBUG =1 ./install.sh --skip-user-creation --no-report-self-hosted-issues --skip-commit-check --skip-sse42-requirements

Expected Result

successful exec ./install.sh

Actual Result

Link with the full output

https://gist.github.com/erycson/899cdc2d8cc3b60488b4a624901d7e66

I want to record some important points that might not appear in the logs:

1. I’m running ./install.sh inside a container, because I use Windows and .sh scripts can’t be executed natively. I actually want it to run inside a container for portability, since I have a project that uses Sentry for everything.

2. I always have to run the process twice, because on the first run I get the following error:

2025-07-15T11:49:26.714637Z  INFO relay_config::config: generating new relay credentials
2025-07-15T11:49:30.158150Z ERROR relay_log::utils: error=no stored credentials

Failed to create relay credentials in relay/credentials.json.
--- credentials.json v ---------------------------------------
{"secret_key":"ASl0qN8XVaOLmDQjvs56SBsRrlLB0Dt5QL6d1kNqVGo","public_key":"a_PbDfiLyH46r5x25sDjvHflrCxB6vhI7i0otfy2kVE","id":"4cd262a4-2545-45fe-a6e4-a77606b48273"}
--- credentials.json ^ ---------------------------------------

3. Then I run ./install.sh again and it proceeds normally until it throws the following error (summarized), which is the reason I opened this issue:

Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/etc/sentry/entrypoint.sh": stat /etc/sentry/entrypoint.sh: no such file or directory: unknown
Error in install/set-up-and-migrate-database.sh:14.
'$dcr web upgrade --noinput --create-kafka-topics' exited with status 1
-> ./install.sh:main:42
--> install/set-up-and-migrate-database.sh:source:14

Event ID

No response

[aldy505]

How did you run the install script inside a container? Did you provide a way for the container to access the Docker socket?

[erycson]

Como você executou o script de instalação dentro de um contêiner? Você forneceu uma maneira para o contêiner acessar o soquete do Docker?

How did you run the install script inside a container? Did you provide a way for the container to access the Docker socket?

My Dockerfile:

FROM python:3.11-slim

# Install system dependencies
RUN apt-get update && apt-get install -y \
    build-essential \
    curl \
    gcc \
    g++ \
    git \
    libpq-dev \
    python3-dev \
    libxml2-dev \
    libxslt1-dev \
    zlib1g-dev \
    pkg-config \
    libffi-dev \
    libssl-dev \
    docker.io \
    && rm -rf /var/lib/apt/lists/*

# Install Docker Compose
RUN curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
RUN chmod +x /usr/local/bin/docker-compose

# Clone Sentry repository
RUN mkdir -p /opt/sentry-self-hosted \
    && git clone --branch 25.6.2 --depth 1 https://github.com/getsentry/self-hosted.git /opt/sentry-self-hosted \
    && chmod -R 777 /opt/sentry-self-hosted

# Set working directory
WORKDIR /opt/sentry-self-hosted


# Copy configuration files
COPY .docker/sentry/sentry.conf.py .docker/sentry/config.yml /opt/sentry-self-hosted/sentry/
COPY .docker/sentry/.env /opt/sentry-self-hosted/

# Set volume for data persistence
VOLUME /data

# Start Sentry
CMD ["tail", "-f", "/dev/null"]

My docker-compose.yml

services:
  sentry:
    build:
      context: .
      dockerfile: .docker/sentry/Dockerfile
    privileged: true
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    labels:
      - "traefik.http.routers.sentry.rule=Host(`sentry.local`)"
      - "traefik.http.routers.sentry.entrypoints=web"
      - "traefik.http.routers.sentry.middlewares=cors_headers@docker"
      - "traefik.http.services.sentry.loadbalancer.server.port=9000"
      - "traefik.http.middlewares.cors_headers.headers.customResponseHeaders.addVaryHeader=true"
      - "traefik.http.middlewares.cors_headers.headers.accessControlAllowCredentials=true"
      - "traefik.http.middlewares.cors_headers.headers.accessControlAllowOriginList=*"
      - "traefik.http.middlewares.cors_headers.headers.accessControlAllowHeaders=sentry-trace,baggage"
      - "traefik.http.middlewares.cors_headers.headers.accessControlAllowMethods=GET,POST,PUT"
      - "traefik.http.middlewares.cors_headers.headers.accessControlExposeHeaders=sentry-trace,baggage"
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"
        labels: "sentry"

My `docker-compose` file contains other services, but I only included the Sentry service here.

After the service starts, I enter the Sentry container and run:

```bash
./install.sh --skip-user-creation --no-report-self-hosted-issues --skip-commit-check --skip-sse42-requirements

Note that I’m using /opt/sentry-self-hosted instead of /etc/sentry. This is because I’m testing other configurations in an attempt to resolve the issue.

[aldy505]

I wonder what happen during this step

# Copy configuration files
COPY .docker/sentry/sentry.conf.py .docker/sentry/config.yml /opt/sentry-self-hosted/sentry/
COPY .docker/sentry/.env /opt/sentry-self-hosted/

My guess is that you are overriding this file.

I'm very curious on why you want your self-hosted Sentry to be setup this way. I personally don't recommend this approach as you'll be having a hard time upgrading your instance.