Every container, and everything about it.
Grouped by compose project, with live CPU and memory per container. Open one and you get its logs, health, events, environment, processes, files, networks and a shell, each in its own tab.
What is a container, really?Read the comic: every cook at their own station, and what the app notices when something is quietly wrong →What you can do
Grouped the way you work
Containers from one compose project stay together, and the tasks of a swarm stack with their stack, the old ones folded behind one line. A project that also has containers on another machine says where, and opens as a diagram. Add your own groups next to them, or let the labels you already set for Dozzle, Homepage or Dockpeek name a container and group it. If you like, the icon from an Unraid or Homepage label shows next to its name.
Bulk actions
Start, stop, restart, pause and remove, for one container or a whole selection. Mark rows with the space bar, like k9s: arrows or j and k move, space marks, Shift with an arrow marks while moving, Shift+click marks a range, and Ctrl+A marks everything. Enter opens the row. And "stop immediately" for the one that won’t.
Files
Browse a container, download and upload by drag and drop, edit a small text file with a conflict check, and rename, remove or add a folder.
Logs from a point in time
The last hour, since the start, or around a crash. Save the whole log as a file.
Adjust without recreating by hand
Environment, ports, restart policy, volumes and folders, and the health check, next to memory and CPU limits. If a change fails, the app puts the old container back.
A memory limit that fits
From a week of measurements the Stats tab proposes a memory limit: the peak times one and a half, rounded up. Apply opens the limit dialog with that number filled in.
Restarts itself when unhealthy
Turn it on for a container with a health check. The app restarts it right away, then after 2 and 8 minutes, and stops after three times in an hour; the Health tab says when it happened.
Duplicate
A copy of a container with its own ports and a copy of its volumes.
Save as image
Commit a container to an image, with a clear list of what does not come along.
Run command or compose service
Copy the docker run command of an existing container, or the same as a compose service. Choose several and write them as one compose file.
Links to the domain
For a container behind Traefik or Caddy, a link next to its name to the domain its labels name: https when the router has tls, http otherwise. The same on the Ports page and in the header of the container, and the labels of Traefik v1 count too.
Fixed local domains
Switch it on in Settings, and every container with a port on this computer gets an address such as web.shop.docker.localhost or redis.docker.localhost, through a small Traefik helper on 127.0.0.1 that the app starts and keeps on every network. Browsers send *.localhost to your own computer, so no DNS is needed. Optionally https, with a local certificate authority of its own that may only sign for docker.localhost; trust it once in Windows. A container Traefik cannot reach gets no link.
IP addresses
The address of a running container on each of its networks sits in the list.
Disk, throttling and processes
The Stats tab of a container also shows disk reads and writes, how often and for how long the CPU limit held it back, and how many processes it runs.
A diagnosis for an issue
One click copies a diagnosis, with secrets left out, ready to paste into an issue.
A diagnosis of an image or a volume
The same one-click diagnosis for an image and for a volume, with secrets left out, ready to paste into an issue.
Filter like k9s
The search box of the lists takes several words that all have to match, !word to leave something out, "a phrase", and /regular expression/, also with spaces and flags such as /time ?out/i. A tooltip explains it. The Ports page, the logs and Ctrl+K search the same way.
It notices
Running, but not really connected.
A container can keep running after its network was removed and created again, or after a start that failed on a taken port. The app spots both, tells you why it happens, and offers the fix. A container that never got past created says why too. When a port is taken, it tells you who is on it, and if that is not a container, where to look on the machine the engine runs on.
All features