Home › Utilities › ContainerPeek
Available nowWhich containers and VMs are running, and what are they costing me?

ContainerPeek See your containers and VMs, their ports and what they use.

Docker and Podman containers with ports, CPU and memory, safe start/stop/remove, and the VMs behind them.

At a glance
Status
Available now
Price
Free · MIT license
Requires
macOS 13 or later
Permissions
None
Network
Not used
Account
Not needed
Telemetry
None

The problem

Something is holding port 5432 and the fans are on. Is it a container, which one, and is it Docker Desktop, OrbStack, Colima or a forgotten VM eating the memory? Answering takes docker ps, docker stats, limactl list and Activity Monitor, in a terminal you may not have open.

The solution

ContainerPeek asks the container tools you have installed and shows every container with its image, state, published ports, Compose project, and the CPU and memory the engine reports. It can start, stop, restart, pause, resume or remove a container: it checks first that it is still the same container in a state where that makes sense, and remove never deletes volumes or images. It also lists Lima, Colima, Tart and Parallels VMs, and the hypervisor processes on your Mac with what they really cost in CPU and memory.

Features

  • Docker and Podman containers, running first, with image, state, ports and Compose project
  • CPU and memory per container, as the engine reports them, and the Docker context in use (Docker Desktop, OrbStack, Colima, Rancher Desktop)
  • Start, Stop, Restart, Pause, Resume and Remove, each re-checked against the live container; Stop, Restart and Remove ask first
  • The last 200 log lines of a container on request, shown only on screen
  • Lima, Colima, Tart and Parallels Desktop virtual machines with CPUs, memory and disk
  • The hypervisor processes on your Mac (Virtualization framework, QEMU, Parallels, VMware) with their CPU and memory

How it works

  1. Open ContainerPeek from the launcher.
  2. Search by name, image, project or port, and open a container for its details and actions.
  3. Scroll down for virtual machines and what they cost your Mac.

Privacy

Reads
  • Containers and their resource use from the docker and podman tools you have installed (ps and stats), only while ContainerPeek is open
  • Virtual machines from limactl, colima, tart and prlctl when installed
  • CPU time and memory of hypervisor processes your user can inspect (libproc)
  • A container's last log lines only when you ask for them
Access
None. Actions run the engine's own start, stop, restart, pause, unpause or rm command as your user, after you confirm; rm never removes volumes or images.
Network
Everything stays on your Mac: no account, no telemetry, no network access.

Read the full privacy statement →

Installation

ContainerPeek is part of MacPeek. Install MacPeek, open Manage utilities and make sure ContainerPeek is switched on (it is on by default). There is nothing separate to download.

Open source

MacPeek and every utility in it are MIT-licensed. Read the code on GitHub, or see how a utility is built.

Frequently asked questions

What does ContainerPeek do?

ContainerPeek asks the container tools you have installed and shows every container with its image, state, published ports, Compose project, and the CPU and memory the engine reports. It can start, stop, restart, pause, resume or remove a container: it checks first that it is still the same container in a state where that makes sense, and remove never deletes volumes or images. It also lists Lima, Colima, Tart and Parallels VMs, and the hypervisor processes on your Mac with what they really cost in CPU and memory.

What does ContainerPeek read from my Mac?

Containers and their resource use from the docker and podman tools you have installed (ps and stats), only while ContainerPeek is open; Virtual machines from limactl, colima, tart and prlctl when installed; CPU time and memory of hypervisor processes your user can inspect (libproc); A container's last log lines only when you ask for them.

Does ContainerPeek need any permissions?

None. Actions run the engine's own start, stop, restart, pause, unpause or rm command as your user, after you confirm; rm never removes volumes or images.

Does ContainerPeek send my data anywhere?

No. Everything stays on your Mac: no account, no telemetry, nothing is sent anywhere.

Is ContainerPeek free?

Yes. ContainerPeek is part of MacPeek, which is free and open source under the MIT license.

Get ContainerPeek with MacPeek.

Free and open source.