Containers

The Containers page lists every container running on every host managed by dockmesh. Use it when you need to drop one level below the stack abstraction — direct container access for debugging, live stats, or emergency restart.

The list view

Containers in the sidebar shows all containers. Default columns:

Column	Description
Name	Container name, clickable into the detail view
Image	Image tag with digest tooltip on hover
Status	Running, exited, restarting, paused, with uptime
Stack	Parent Compose project (if any)
Host	Which Docker host the container is on
CPU / Memory	Live stats from the Docker stats stream
Ports	Published host ports with click-to-copy

Sort by clicking any column. Filter by host via the top dropdown. Search by name, image, or stack.

Detail view

Clicking a container opens its dedicated page with up to seven tabs (depending on your role):

Overview

Identity card — image digest, created time, command, entrypoint, restart policy, health-check status, labels, env vars (with a Show secrets toggle) — alongside live resource charts streamed via WebSocket:

CPU usage (1-minute trailing sparkline)
Memory (RSS + cache)
Network I/O (rx/tx per second)
Throughput totals + averages over the buffer

Logs

Live-streaming logs via WebSocket. Tail history depth is configurable, follow toggles between one-shot and continuous, and a per-line search box filters the visible window. Logs come straight from the agent — no aggregation layer, no retention beyond what Docker itself keeps.

Terminal (requires `containers.exec`)

Browser-based interactive shell using docker exec + WebSocket. Defaults to /bin/sh. Full xterm.js terminal: copy/paste, resize, clear, automatic reconnect on disconnect.

Inspect

Full docker inspect JSON in a viewer — toggle between pretty and raw mode.

Network

Connected networks, IP addresses, aliases, exposed ports, and a per-network breakdown of the container’s network settings.

Files

Container filesystem browser. Lists one directory level at a time using a tar-stream walk (works on scratch / distroless images), with file preview, download, edit, and upload — write actions are gated on containers.exec because writing into a running container is effectively code injection.

Updates (local hosts only, requires `containers.update`)

Image-update preview + apply + rollback. Compares the running image digest against the registry, shows the diff, and lets you redeploy with one click. Rollback walks the update-history table.

Header actions

The lifecycle actions are buttons in the page header, not a separate tab:

Start / Stop / Restart — graceful with configurable timeout
Pause / Unpause — freeze the container without killing it
Kill — sends a signal (default SIGKILL)
Remove — stops then removes (volumes are preserved)

All actions are RBAC-gated and written to the audit log.

Bulk operations

Select multiple containers with the checkbox column, then apply:

Start all
Stop all
Restart all
Remove all

Bulk operations run in parallel with progress streaming.