ContainerPeek
How to use ContainerPeek to see Docker and Podman containers, their ports, CPU and memory, start or stop them safely, and see Lima, Colima, Tart and Parallels VMs.
The question it answers: which containers and VMs are running, and what are they costing me?
What you see
- Containers for each engine you have installed, Docker and Podman, with the Docker context in use (Docker Desktop, OrbStack, Colima, Rancher Desktop). Running containers come first, with image, state, published ports, Compose project, and the CPU and memory the engine reports.
- If the engine is installed but not running, ContainerPeek says so, rather than showing an empty list.
- Virtual machines from Lima, Colima, Tart and Parallels Desktop, with CPUs, memory and disk.
- Hypervisor processes on your Mac (Apple’s Virtualization framework, QEMU, Parallels, VMware) with the CPU and memory macOS counts for them: what a VM really costs, whichever tool started it.
Managing a container
Open a container to see its details and the actions that make sense for it: Start, Stop, Restart, Pause, Resume or Remove. Stop, Restart and Remove ask first. Before acting, ContainerPeek looks the container up again and does nothing if it is gone, has been renamed or is now in a different state. Remove deletes the container only: never its volumes or its image.
Images in MacPeek Remote
In MacPeek Remote, a Mac’s Containers Peek has an Images list for its Docker engine (Docker Desktop or a Docker command-line install). It shows each image’s name and tag, size and age, and which containers use it.
- Delete removes an image, or just one tag of an image that has several. It never forces: Docker refuses to delete an image a container still uses, and you see its message. Removing one of several tags only removes that tag, so it succeeds even while a container uses the image.
- Run starts a detached container from an image. You can choose a name and the ports to publish. Ports are published on that Mac only unless you turn on Expose to the network. Nothing is pulled, and no volumes, environment variables or extra privileges are added.
Both need Allow actions on that Mac and a console with View and act access, appear in the Mac’s activity log, and look the image up again first, so they do nothing if it has changed. Pulling, loading and building images are not offered, and the Mac needs a MacPeek version that includes this feature.
Logs
Press Show recent logs to see the last 200 lines a container printed. Logs can contain secrets, so they are shown on screen only, never saved or logged, and forgotten when you leave ContainerPeek.
Good to know
- ContainerPeek uses the tools you already have (
docker,podman,limactl,colima,tart,prlctl) from Homebrew’s folders and the apps’ own folders. It never installs anything. - It reads every few seconds only while its screen is open. The launcher summary lists containers without asking for their resource use.