TL;DR: If the Middleware Docker agent does not report data, check two things first. Mount /var/run/docker.sock into the container; without the socket the agent cannot collect container metrics and may exit. Then confirm only one agent runs on the host: two agents with the same hostname fight each other and one silently wins.

If the Middleware Docker agent does not report data, check two things first. Mount /var/run/docker.sock into the container; without the socket the agent cannot collect container metrics and may exit. Then confirm only one agent runs on the host: two agents with the same hostname fight each other and one silently wins. If the container exits immediately, run docker logs on it instead of restarting blind; the log line names the cause (bad key, no socket, no network). The agent needs outbound HTTPS on port 443 to its target, so also confirm the firewall allows it.

Context: Official docs (docs.middleware.io, Docker agent installation): documents the two install killers: the Docker socket must be mounted into the agent container, and only one agent may run per host. A container that starts and exits silently needs its logs inspected.

## When to use
You hit exactly this: Middleware Docker agent: mount the socket, run only one per host in Middleware Docker agent.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Middleware Docker agent.

## Edge cases
- Then confirm only one agent runs on the host: two agents with the same hostname fight each other and one silently wins.
- A container that starts and exits silently needs its logs inspected.