Skip to main content

Running MAC Without the Package

If you are evaluating MAC from a source checkout, you can run the CLI directly from the build tree.

From a Source Checkout​

~$ make build
~$ make cli
~$ ./cli/mac env set MAC_CONFIG_DIR=$PWD/deploy
~$ ./cli/mac start all

The same env / pull / start / stop / status / clean subcommands all work; only the binary path and MAC_CONFIG_DIR differ.

Direct docker compose Usage​

The CLI is a convenience wrapper around docker compose plus the agent registration handshake. If you prefer to drive Compose yourself:

~$ cd /etc/mango/mac          # or your $MAC_CONFIG_DIR
~$ docker compose -f docker-compose.master.yml up -d
~$ docker compose -f docker-compose.agent.yml  up -d

Note that bypassing mac start agent skips the auto-registration step — the agent will only appear on the master once it is successfully scraped by Prometheus.

When This Matters​

  • Reproducing a customer issue from a specific git ref
  • Hot-patching the api-server or web-ui in a lab
  • Running MAC images on Kubernetes via your own manifest