Skip to main content

Running MAC Without the Package

Build from the required revision with its toolchain and image dependencies.

From a Source Checkout​

make cli
export MAC_CONFIG_DIR="$PWD/deploy"
./cli/mac start all --local --wait

Export MAC_CONFIG_DIR before loading configuration. mac env set MAC_CONFIG_DIR=... persists it; prefer export to avoid changing shared-home settings. deploy/env may need registry credentials or external-image overrides.

--local builds services/ and fetches external images. make build and mac build <mode> only build; mac pull <mode> --local also fetches dependencies. Inspect references with mac images.

Keep credentials outside deploy/env, in user overrides or a dedicated configuration directory. Use the same valid node token on master and agents.

Direct docker compose Usage​

Initial mac start prepares networking, Prometheus/Loki config volumes, image pins, GPU profiles, log routing, tokens, and enrollment. Bare Compose up omits these steps; scraping alone does not enroll agents.

Inspect existing services with Compose project mac:

docker compose -p mac -f "$MAC_CONFIG_DIR/docker-compose.master.yml" ps
docker compose -p mac -f "$MAC_CONFIG_DIR/docker-compose.master.yml" logs api-server

GPU exporters require the nvidia/amd profiles. Direct Compose neither selects them nor loads the CLI’s three configuration layers automatically.

When This Matters​

  • Reproduce behavior at a specific source revision.
  • Evaluate local service changes in an isolated deployment.
  • Inspect Compose state without changing node enrollment.