>sentry

sentry

An application monitoring and error tracking tool used to identify, triage, and resolve issues in real time across distributed sstems.

postgres

redis

nginx

kafka

What is sentry image?

The sentry image provides a full instance of Sentry, an open-source platform for error tracking, performance monitoring, and exception aggregation. Sentry collects and centralizes application errors, stack traces, and performance data from multiple environments and frameworks — including Python, JavaScript, Go, Java, and Rust — providing developers with detailed insights into production issues.

This image includes Sentry’s web interface, background workers, and API services, allowing teams to self-host a complete instance of the platform. It’s often used in Kubernetes, Docker Compose setups, or on bare metal for organizations that require full control over data. Sentry is especially valuable in modern microservice environments, offering distributed tracing and contextual error tracking that helps developers quickly connect backend failures with frontend events.

How to use this image

The sentry image can be deployed as a single container for evaluation or in a multi-service stack with Postgres, Redis, and Kafka for production-scale usage.

Run a standalone instance (development or testing):

docker run -d -p 9000:9000 sentry

‍Run with dependencies via Docker Compose (simplified):

version: '3'
services:
  sentry:
    image: sentry
    ports:
      - "9000:9000"
    environment:
      - SENTRY_SECRET_KEY=<secret>
      - SENTRY_DB_USER=postgres
      - SENTRY_DB_PASSWORD=postgres
      - SENTRY_REDIS_HOST=redis
    depends_on:
      - redis
      - postgres

  redis:
    image: redis

  postgres:
    image: postgres

Initialize the database before first use:

docker-compose run sentry upgrade

Logs are written to stdout and accessible through docker logs. By default, the Sentry web UI listens on port 9000. Production deployments should include worker processes and caching for performance.

Image variants

Published under getsentry/sentry, the image is available in multiple variants:

getsentry/sentry:latest
Tracks the latest stable release.
Suitable for local or evaluation environments.‍
getsentry/sentry:<version>
Tagged by version (e.g. 24.8.1, 23.10.0).
Recommended for production deployments to maintain stability.‍
getsentry/sentry:onpremise
Bundled variant configured for self-hosted setups with Redis, Postgres, and Kafka integration.
Commonly used in enterprise or air-gapped environments.‍
getsentry/sentry:nightly
Development build with the latest commits.
Use for testing or contributing to Sentry’s upstream development.

Sentry images are updated frequently alongside backend dependency upgrades. For production, pin a versioned tag and ensure supporting services (Postgres, Redis, Kafka) are on compatible releases.

Interested in base images that start and stay clean?

Oops! Something went wrong while submitting the form.