Docker Compose

Prerequisites

Install Docker and Docker Compose before continuing.

Self-contained deployment (recommended)

This option deploys Rootprint together with PostgreSQL and a bundled Quickwit search engine. Download the Compose file and start the services:

curl -o docker-compose.yml https://docs.rootprint.io/files/docker-compose.full.yaml
docker compose up -d

Show docker-compose.yml

services:
  db:
    image: postgres:17
    restart: unless-stopped
    environment:
      POSTGRES_USER: rootprint
      POSTGRES_PASSWORD: rootprint   # change in production
      POSTGRES_DB: rootprint
    volumes:
      - rootprint-db:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U rootprint"]
      interval: 5s
      timeout: 3s
      retries: 10

  quickwit:
    image: quickwit/quickwit:v0.9.1
    restart: unless-stopped
    volumes:
      - rootprint-quickwit:/quickwit/qwdata
    command: ["run"]
    healthcheck:
      test: ["CMD-SHELL", 'bash -c "echo > /dev/tcp/localhost/7280"']
      interval: 10s
      timeout: 5s
      retries: 10

  rootprint:
    image: ghcr.io/rootprint/rootprint:latest
    restart: unless-stopped
    depends_on:
      db:
        condition: service_healthy
      quickwit:
        condition: service_healthy
    environment:
      DATABASE_URL: postgres://rootprint:rootprint@db:5432/rootprint
      QUICKWIT_URL: http://quickwit:7280
      ORIGIN: http://localhost:8282   # change to your public URL
    ports:
      - "8282:8282"
    healthcheck:
      test: ["CMD", "bun", "-e", "fetch('http://localhost:8282/api/health').then(r => process.exit(r.ok ? 0 : 1), () => process.exit(1))"]
      interval: 10s
      timeout: 5s
      retries: 5

volumes:
  rootprint-db:
  rootprint-quickwit:

This starts three containers:

Rootprint: the web UI, exposed on port 8282.
PostgreSQL: Rootprint application state, stored in the rootprint-db Docker volume.
Quickwit: the bundled search engine, reachable only from the Compose network by default.

Run docker compose ps to confirm all containers are healthy, then open http://localhost:8282.

Use S3 for storage

By default, index data lives in the rootprint-quickwit Docker volume, and removing that volume deletes your logs. To store it in S3 or S3-compatible object storage, add these variables to the quickwit service:

services:
  quickwit:
    image: quickwit/quickwit:v0.9.1
    environment:
      QW_DEFAULT_INDEX_ROOT_URI: s3://your-bucket-name/indexes
      QW_METASTORE_URI: s3://your-bucket-name/metastore
      AWS_ACCESS_KEY_ID: ${AWS_ACCESS_KEY_ID}
      AWS_SECRET_ACCESS_KEY: ${AWS_SECRET_ACCESS_KEY}
      AWS_REGION: us-east-1

Set both variables to paths within the same bucket. The bucket must already exist. This setup stays single-node. For a multi-node Quickwit cluster, move the metastore to PostgreSQL. See Scaling beyond a single node.

Other storage backends

Other backends use the same two variables with a different URI scheme and credentials.

Backend	URI scheme	Credentials
AWS S3	`s3://bucket/path`	`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_REGION`
Azure Blob Storage	`azure://container/path`	`QW_AZURE_STORAGE_ACCOUNT`, `QW_AZURE_STORAGE_ACCESS_KEY`
Google Cloud Storage	`s3://bucket/path` with `flavor: gcs`	HMAC keys via `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY`
MinIO / Garage / DO Spaces	`s3://bucket/path` with matching `flavor`	Provider-specific keys via `AWS_ACCESS_KEY_ID` / `AWS_SECRET_ACCESS_KEY` and `QW_S3_ENDPOINT`

For Google Cloud Storage and other S3-compatible providers, set flavor in the Quickwit storage config. See the Quickwit storage reference for the YAML structure and the full env-var list.

Exposing Quickwit on internal networks

If other services on your internal network need to reach Quickwit directly, add these port bindings to the quickwit service:

ports:
  - '7280:7280'
  - '7281:7281' # gRPC

Quickwit has no authentication. Never expose it on a public or untrusted network. Restrict access at the network or firewall level.

Connect to an existing Quickwit instance

Rootprint requires Quickwit 0.9.0+; earlier releases are not supported. Check your version with curl http://your-quickwit-host:7280/api/v1/version.

If you already have a Quickwit cluster running, deploy Rootprint with PostgreSQL and point it at your Quickwit instance. Download the standalone Compose file:

curl -o docker-compose.yml https://docs.rootprint.io/files/docker-compose.standalone.yaml

Open docker-compose.yml and set QUICKWIT_URL to the REST API endpoint of your Quickwit instance:

environment:
  QUICKWIT_URL: http://your-quickwit-host:7280

Show docker-compose.standalone.yml

services:
  db:
    image: postgres:17
    restart: unless-stopped
    environment:
      POSTGRES_USER: rootprint
      POSTGRES_PASSWORD: rootprint   # change in production
      POSTGRES_DB: rootprint
    volumes:
      - rootprint-db:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U rootprint"]
      interval: 5s
      timeout: 3s
      retries: 10

  rootprint:
    image: ghcr.io/rootprint/rootprint:latest
    restart: unless-stopped
    depends_on:
      db:
        condition: service_healthy
    environment:
      DATABASE_URL: postgres://rootprint:rootprint@db:5432/rootprint
      QUICKWIT_URL: http://your-quickwit-host:7280   # Quickwit 0.9.0+ required
      ORIGIN: http://localhost:8282   # change to your public URL
    healthcheck:
      test: ["CMD", "bun", "-e", "fetch('http://localhost:8282/api/health').then(r => process.exit(r.ok ? 0 : 1), () => process.exit(1))"]
      interval: 10s
      timeout: 5s
      retries: 5
    ports:
      - "8282:8282"

volumes:
  rootprint-db:

Then start the service:

docker compose up -d

Run docker compose ps to confirm both containers are healthy, then open http://localhost:8282.

Configuration

Customize the deployment by setting environment variables under the environment key of the rootprint service. See the environment variables reference for the full list, including the database URL, public origin, Quickwit endpoint, and session secret.

Next steps

With Rootprint running, head to Send logs to start ingesting data.

Get Started

Send Logs

Traces

Search Logs

Manage Rootprint

Prerequisites

Self-contained deployment (recommended)

Use S3 for storage

Other storage backends

Exposing Quickwit on internal networks

Connect to an existing Quickwit instance

Configuration

Next steps

​Prerequisites

​Self-contained deployment (recommended)

​Use S3 for storage

​Other storage backends

​Exposing Quickwit on internal networks

​Connect to an existing Quickwit instance

​Configuration

​Next steps

Prerequisites

Self-contained deployment (recommended)

Use S3 for storage

Other storage backends

Exposing Quickwit on internal networks

Connect to an existing Quickwit instance

Configuration

Next steps