Everyday
Containers
The table, and the full lifecycle behind it.
Columns, in order
- Name · Image · State · Health · Uptime · Restarts · CPU · Memory · Net I/O · Disk I/O · IP · Ports · Auto-update · Stack · Actions.
- Sortable, with a count badge, a search box, a status filter and per-row action icons.
- The Stack column comes from the container's own Compose label, so grouping needs no Compose implementation at all.
What you can do
- The full lifecycle: create, start, stop, restart and remove, each behind a confirmation.
- Create with configuration, and change resources or restart policy in place.
- Attach and detach networks.
- Check for updates, update all of them at once, and prune what is no longer needed.
- Every action writes its audit entry before it runs and updates it with the outcome — so a crash still leaves evidence the action was requested.
What the connection costs you
- Name, image, state, health, uptime, IP, ports and stack all come free with the container listing.
- Restart counts cost one inspect per container; the four live metric columns cost one streaming subscription each.
- On a host that forbids TCP forwarding, MangoDock falls back to running the CLI over SSH, and the live columns plus health and IP cannot be produced at all.
- In that case they are greyed out and the connection chip says why. They are never rendered blank, because a blank port column reads as "no ports" rather than "not available".
Air-gapped
- Listing, lifecycle and live metrics all talk to your own daemons and nothing else.
- Checking for updates asks a registry. Point it at your internal mirror under Settings ▸ Credentials and the check follows the mirror.
- A check against a registry the network cannot reach gives up after fifteen seconds and skips that registry's other images for the rest of the run, so it never stalls.