Compose

The compose command group works against existing Compose projects (anything with the com.docker.compose.project label) and can also deploy a fresh project from a compose file.

List projects

dockerman compose list
dockerman compose list --pretty

Returns project name, container count, status, and base path.

Lifecycle

dockerman compose up myproject --detach
dockerman compose stop myproject
dockerman compose start myproject
dockerman compose restart myproject --service web
dockerman compose remove myproject --remove-volumes --yes

up, stop, start, and restart all accept the standard global flags:

compose up accepts --detach (default) or --attach. The current implementation waits for the Compose process and returns its captured output; it does not stream each log line live.

compose remove (also aliased as compose down) is destructive and needs --yes. --remove-volumes is passed through the container-removal path and does not enumerate and delete every named volume in the project.

Pull

dockerman compose pull myproject --json
dockerman compose pull myproject --service web --json

Streams pull progress as one NDJSON envelope per layer. Use --json for machine-readable output, omit it for the human-friendly progress lines.

Deploy from a compose file

dockerman compose deploy myproject ./docker-compose.yml \
  --env DATABASE_URL=postgres://... \
  --env LOG_LEVEL=info

deploy takes a project name plus a compose file path. The CLI reads the file and the daemon writes its contents to a temporary directory before invoking Compose. Relative build contexts and bind paths therefore do not reliably resolve against the original file's parent; use absolute paths or deploy from an existing project with an explicit working directory.