Docker Monitor architecture
Deploy the Docker Monitor Agent container on each Docker host. The mobile app connects to the agent with a bearer token for authenticated API operations.
Docker Monitor uses a containerized agent setup for onboarding and operations.
Run the commands below on your Docker host. Replace the image reference if you publish your own tag.
TOKEN="$(openssl rand -hex 32)"
IMAGE="appleberryd/dockermonitor-agent:0.1.1"
docker rm -f docker-monitor-agent >/dev/null 2>&1 || true
docker run -d \
--name docker-monitor-agent \
--restart unless-stopped \
-p 9876:9876 \
-e AGENT_AUTH_TOKEN="$TOKEN" \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
-v /:/host:ro \
--security-opt no-new-privileges:true \
--read-only \
--tmpfs /tmp \
--memory 128m \
--cpus 0.5 \
"$IMAGE"
echo "AGENT_AUTH_TOKEN=$TOKEN"curl http://localhost:9876/agent/health
curl -H "Authorization: Bearer $TOKEN" http://localhost:9876/version
curl http://localhost:9876/version # expected: 401If health returns 200 and unauthorized version returns 401, your agent auth flow is working correctly.
To rotate credentials, generate a new token, restart the container with updated `AGENT_AUTH_TOKEN`, then update the token in the app server profile.
Use SSH tunneling if your agent port is not publicly reachable. Tunnel directly to the agent service endpoint.
ssh -L 19876:127.0.0.1:9876 user@your-server
# In Docker Monitor:
# Host: 127.0.0.1
# Port: 19876
# Agent token: same AGENT_AUTH_TOKEN| Endpoint | Auth | Purpose |
|---|---|---|
| `/agent/health` | No | Liveness and Docker connectivity state |
| `/agent/stats` | Yes | Host + Docker metrics payload |
| `/containers/*`, `/images/*`, `/info`, `/version` | Yes | Docker operations used by app flows |
Symptoms: `pull access denied` or `manifest unknown`.
If your setup is still failing, send your deployment command and `docker logs docker-monitor-agent` output.
Contact Support