Run services

Run a compose stack on the host and see which services are up, healthy and listening.

With DOCKER_HOST or a context pointing at your host, docker compose runs your whole stack there. The dashboard shows which services are up, whether they are healthy, what they use, and which ports they publish.

Run a stack

A typical app with a database. Health checks are optional, but they are what makes a service show as healthy or unhealthy.

compose.yaml
services:
  api:
    build: .
    ports: ["3000:3000"]
    environment:
      DATABASE_URL: postgres://postgres:postgres@db:5432/app
    depends_on:
      db:
        condition: service_healthy
    healthcheck:
      test: ["CMD", "curl", "-fs", "http://localhost:3000/health"]
      interval: 10s
      retries: 3

  db:
    image: postgres:17
    environment:
      POSTGRES_PASSWORD: postgres
      POSTGRES_DB: app
    volumes:
      - pgdata:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD", "pg_isready", "-U", "postgres"]
      interval: 5s

volumes:
  pgdata:
your terminal
docker compose up -d --build
docker compose ps
docker compose logs -f api

build: . sends the folder to the host and builds there. Named volumes such as pgdata live on the host and survive restarts and stops. A bind mount like ./src:/app would mount the host's disk, not your folder; to edit code live, sync it in with compose watch or Mutagen.

See what is running

On the Docker hosts page, press Stats on a host. Under the machine's CPU, memory, disk and network, Containers lists every running container:

ColumnShows
ContainerThe compose service name, or the container name, with its image underneath. Containers are grouped by compose project.
UpHow long it has run, as docker ps says it, with a dot for its health check: green healthy, amber starting, red unhealthy.
PortsEach published port, as the host port and, when different, the container port. Click one to copy the command that opens it on your machine.
CPUIts share of the whole machine over the last minute.
MemoryWhat it uses now, counted as docker stats counts it.

The list refreshes once a minute while the host runs, and a stopped host shows what was running when it stopped. For the live state, use docker compose ps and docker stats from your terminal; they answer from the host.

See what fills the disk

The Disk column shows each host's used and free space; with several hosts, the total for all of them is above the list. Click a host's bar for two views:

  • Overview splits the disk into images, volumes, build cache, containers' own changes, other files and the system's own files, and lists the largest folders, files, images and volumes.
  • Browse walks the disk folder by folder, largest first, with each entry's size, item count and last change.

The host scans its disk when the space in use has changed by a GB since the last scan, at most every 30 minutes, and at the lowest priority, pausing while your own work is busy with the disk; press Rescan for a fresh look. A stopped host shows its last scan. Only names and sizes are read, never what files hold, and entries under 1 MB are counted in their folder as smaller items. To free space, docker builder prune removes unused build cache and docker image prune images nothing uses.

Several stacks on one host

Each folder is its own compose project, so two stacks don't replace each other's containers. They do share the host's ports: two services can't both publish 3000. Change one side's host port, such as "3001:3000", or give each project its own host, as in One host per project.

When the host stops

Containers stop with it, and images and volumes stay. After it starts again, start the stack again with docker compose up -d, or give services restart: unless-stopped to have them start with the host.