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.
Fig. — A container's detail page, with logs from the last hour.
What you can do
Grouped the way you work
Containers from one compose project stay together. Add your own groups next to them.
Bulk actions
Start, stop, restart, pause and remove, for one container or a whole selection. 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.
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.
A diagnosis for an issue
One click copies a diagnosis, with secrets left out, ready to paste into an issue.
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. When a port is taken, it tells you who is on it.
All features