Autograph
dev

Compose runtimes

Configure autograph when the standard Docker Compose v2 runtime is unavailable.

Standard runtime

The supported default is Docker Engine 20.10 or newer with Docker Compose v2. The generated env/.env.augr already selects it:

env/.env.augr
AUGR_CONTAINER_CLI=docker
AUGR_CONTAINER_COMPOSE_CMD='docker compose'
AUGR_CONTAINER_COMPOSE_VARIANT=

Use docker compose version to check the plugin. Do not use docker compose --version: it can report the Docker Engine version when the plugin is missing.

For Linux, macOS, or WSL2 installation details, see Platforms.

Standalone docker-compose v1

docker-compose v1 is supported from 1.28.0. Configure both the command and the Compose-file variant in env/.env.augr:

env/.env.augr
AUGR_CONTAINER_CLI=docker
AUGR_CONTAINER_COMPOSE_CMD='docker-compose --compatibility'
AUGR_CONTAINER_COMPOSE_VARIANT=.v1

The variant selects compose.v1.yaml instead of compose.yaml. Set it in the file, not only in the shell. Check the installed version with docker-compose --version. --compatibility makes docker-compose v1 apply the CPU and memory limits of the v1 files; without it, these limits are ignored.

Package task limitation

Engine lifecycle and seed app tasks select the configured variant. Package tasks (augr:pkg:*) that invoke Compose still require the v2 plugin. This includes Compose-based chat, shell, and rebuild tasks. The OAuth connect task uses the container CLI directly instead.

Podman Compose

Podman Compose is experimental and has no validated minimum version. Configure it explicitly and validate the target workflow before depending on it:

env/.env.augr
AUGR_CONTAINER_CLI=podman
AUGR_CONTAINER_COMPOSE_CMD='podman compose'

Diagnose configuration

After changing the runtime configuration, run:

terminal
task augr:engine:diagnos:docker

The report shows the configured command, detected Compose type and version, container client version, and host platform. It warns about missing or unsupported commands and standalone v1 releases older than 1.28.0.