Docker

The Docker section covers containers, images, networks, volumes, Compose stacks, and events on the same host as Just Dashboard. It uses the host's Docker Engine connection (JD_DOCKER_HOST, normally the local socket).

Find the cause of a container problemCopy Anchor Link

1. Open Docker → Overview. The identity line ends with Docker's own verdict, such as a container that is failing; selecting it narrows the table to failing containers. The containers using the most processor and memory and the last thing that happened to each are drawn above a live table, failing containers first.
2. Open Containers and choose the affected container. Its Overview tab shows whether it works, how it is reached, and the rest of its Compose project. Usage, Logs, Environment, Storage, Inspect, Configuration, and Shell hold the details.
3. Read how the container stopped before changing it. The dashboard says it in words, such as Out of memory rather than exit code 137, and marks restart loops. A failing health check, frequent restarts, and a published port reachable from every interface point to different remedies.
4. Check Events when you need the sequence of restarts, health transitions, or out-of-memory events and who caused them. Compare the time with Metrics and Logs.

Since 0.7.5 the section no longer produces automatic findings, attention lists, or suggested fixes. It reports what Docker says and leaves the decision to you.

Change a containerCopy Anchor Link

To run something new, use Deployments; the Docker section has no create form. On a standalone container, Configuration lets an administrator edit its replacement specification, preview it, and confirm the replacement, which recreates the container. A container that Compose owns offers Open Compose file instead, because it is changed through its stack. Resource limits can be changed in place from Usage where Docker permits it.

Work with Compose stacksCopy Anchor Link

Open Docker → Stacks, then select a stack. Services, Logs, Files, and Compose file show what it runs and how. Deploy preview shows a file diff and the services expected to be recreated; it is labelled as an expectation because Compose makes the final call. Each deployment records the Compose file, the image digests running just before, and the Git commit. In History, Edit from this version loads an earlier file into the editor so you can roll back deliberately. Environment values are hashed in that record rather than stored in it.

Pull & redeploy pulls images before bringing the new stack up. If the registry pull fails, the running stack stays in place. A stack whose Compose file the dashboard cannot reach is read-only. Stacks can be inspected by signed-in users, while Compose creation, editing, validation, and execution require an administrator in 0.8.4. Deleting a stack asks you to type its name.

Storage and cleanupCopy Anchor Link

Images shows pulled and locally built images and where their size went. Its update check compares the digest behind a mutable tag with the pulled digest; an image is labelled Pinned by digest, Built here, or Not checked when there is no comparison to make, and Check now asks the registries again. Networks shows each network's owner, subnet, and members, and previews what a change would disturb before you attach, detach, or remove. Volumes names what holds each volume and exactly what a prune would delete, so you can find data before changing a container.

Volumes can be browsed from a volume, a container's Storage tab, or a stack's Files tab. If volume browsing returns “not found,” the backend may lack the /var/lib/docker/volumes bind mount that this feature requires. Use Backups before depending on a volume as the only copy of data.

Docker cleanup appears on the overview when more than 1 GiB can be reclaimed and your role may make destructive changes. Each category says what it holds, what removing it gives back, and what it costs. Volumes are never selected by default; choose them only on purpose. On Images, each kind's Reclaim removes only that kind.