Quickstart with Docker Compose
The compose stack runs the whole local service: Valkey, ClickHouse,
PostgreSQL, a one-shot migration container, and oriel serve --role=all.
-
Start the stack from the compose directory.
Terminal window cd deploy/composedocker compose -f local.yml up --build -
Wait for the services to become healthy.
The compose file waits for Valkey, ClickHouse, and PostgreSQL health checks before running
oriel migrate up. Theorielservice starts only after the migration container exits successfully and Valkey is healthy. -
Open the UI and API.
http://localhost:6743 -
Use OTLP endpoints from local applications or collectors.
OTLP gRPC: localhost:4317OTLP HTTP: http://localhost:4318
What starts
Section titled “What starts”| Service | Purpose |
|---|---|
valkey |
Required runtime cache/pub-sub store on port 6379. |
clickhouse |
Telemetry storage, native port 9000, HTTP port 8123. |
postgres |
Metadata and control-plane storage on port 5432. |
oriel-migrate |
One-shot oriel migrate up against both stores. |
oriel |
Long-running oriel serve --role=all. |
Create the first account
Section titled “Create the first account”After the stack is running:
docker compose -f local.yml exec -e ORIEL_BOOTSTRAP_PASSWORD='change-me' oriel \ oriel admin bootstrap --email you@example.comdocker compose -f local.yml exec oriel oriel admin create-workspace --slug demoThe bootstrap command requires a password. Prefer
ORIEL_BOOTSTRAP_PASSWORD; the --password flag is visible in process lists.
Create a project and environment in Settings before sending telemetry.
Stop or reset
Section titled “Stop or reset”Stop the containers:
docker compose -f local.yml downDelete local data volumes:
docker compose -f local.yml down -vDeleting volumes removes PostgreSQL metadata and ClickHouse telemetry. Valkey holds rebuildable runtime cache state in the compose path.