Docker Compose
The public Compose-driven stack lives in agirunner.
Recommended Flow
Section titled “Recommended Flow”- clone
agirunner - copy
.env.exampleto.env - generate and replace the bootstrap secrets
- run
docker compose up -d - open the dashboard at
http://localhost:3000
The default local admin login key comes from
DEFAULT_ADMIN_API_KEY in agirunner/.env. The stack also expects
PLATFORM_SERVICE_API_KEY there so container-manager can talk to the
platform without reusing the human bootstrap key.
Keep PLATFORM_API_PORT=8080 when using the published dashboard image.
The current dashboard bundle is built against that local API URL.
What Compose Brings Up
Section titled “What Compose Brings Up”The top-level stack currently brings up:
- PostgreSQL
- the platform API
- the container manager
- the dashboard
- Docker and socket plumbing used to support execution isolation
Task execution containers are then created later as work is claimed and
executed. The runtime in this stack is an image the container manager
launches for task execution, not a long-running top-level service. By
default that image is the published
ghcr.io/agirunner/agirunner-runtime:latest runtime line.
Why This Matters
Section titled “Why This Matters”This keeps the front-door story simple. First-time users can clone only
agirunner and bring up the product stack without pulling the platform
and runtime source repositories just to get started.