Skip to main content

Installation & Startup

Issues that show up before MAC ever paints a dashboard.

mac command not found after dpkg -i​

The Debian package was installed but your shell hasn't picked up the new binary yet.

  • Open a new shell, or run hash -r in the current one.
  • Verify the install: dpkg -L mango-ai-center | grep /usr/bin/mac.

mac start fails with "permission denied" on /var/run/docker.sock​

Your user is not in the docker group, so it cannot drive the Docker daemon.

~$ sudo usermod -aG docker $USER
~$ newgrp docker     # or log out and back in
~$ mac start all

If you must run as root, prefix with sudo, but mac is intended to run as a non-root user.

Image pull fails with unauthorized or denied​

The configured registry requires credentials, or MAC_REGISTRY points somewhere wrong.

  • Check the value: mac env | grep MAC_REGISTRY.
  • For the public registry, re-authenticate with the partner guest account: docker login repo.mangoboost.io. Credentials are issued by contact@mangoboost.io.
  • For an internal mirror, run docker login <registry-host> once before mac pull.

Some containers stay in restarting state​

~$ mac status
NAME              STATUS
mac-api-server    restarting

Check the container logs:

~$ docker logs mac-api-server

The most common causes:

  • Master unreachable from agent — agent's MASTER_IP is wrong or the master is down.
  • Port already in use — another service is bound to one of MAC's ports. Identify the conflict with sudo ss -tlnp | grep :<port> and either stop the conflicting process or override the port via mac env.
  • Out of disk — Prometheus and Loki refuse to start when their data volume is full.