All pages

Docs · Right-sidebar surfaces

Docker

Availability: macOS. The microVM engine additionally needs macOS 26 on Apple silicon.

The Docker tab (right sidebar, in the More menu) manages containers, images, compose stacks, and ports without leaving the terminal. It works across every runtime it finds — Docker Desktop, OrbStack, Colima, and TRMNLY's built-in engine — and shows them all in one list. The same panel is also embedded in the Conn tab's Containers section; both surfaces share state, so use whichever is closer.

Runtimes

A strip at the top shows one pill per runtime with a status dot. When a CLI is installed but its daemon is down, the pill grows a Start button. The menu on the right picks the preferred runtime — the one new pulls, runs, and compose commands target.

If no runtime is installed at all, the panel offers install links — or, on macOS 26 with Apple silicon, a setup card for the built-in engine, which runs containers as lightweight microVMs with no Docker install. Built-in containers appear in the same lists and answer to the same controls, with two limits: no interactive shell (ask the agent to use container_exec instead) and no compose support.

Containers

Every container shows as a row with its runtime badge, image, and status. Rows refresh every few seconds while the panel is open. Per row:

  • Start / Stop / Restart
  • Logs — expand an inline live tail (one container at a time)
  • Shell — open docker exec -it in the focused terminal, trying bash and falling back to sh
  • Remove — force-removes after confirmation; volumes are kept

Images

Pull an image by reference (postgres:16, nginx) from the field at the top. Each cached image lists its ID, size, and age, and offers:

  • Run — a sheet with optional container name, host:container port mappings (with a free-port suggestion), environment variables, and a remove-on-exit toggle
  • Remove — delete the cached image

Compose

Register a compose project with + by picking a folder containing compose.yaml or docker-compose.yml. Opening the panel also auto-discovers a compose file in the active project's folder. Each project card lists its services and ports and offers up, down, and restart. Removing a card only forgets it in TRMNLY — the compose file on disk is untouched.

Ports

The fourth sub-tab is the master ports table: every host listener, container publish, SSH tunnel, and reservation on one row per port, with conflicts badged. See Ports for the full story.

Agent tools

Tool Approval Use
docker_daemon_status no Which runtimes are installed and running
docker_container_list no Containers on every runtime, stopped ones included (all: false for running only)
docker_container_start / docker_container_stop / docker_container_restart yes Lifecycle by name or ID
docker_container_remove yes Remove a container (volumes kept)
docker_container_logs no One-shot log snapshot (default 200 lines)
docker_images_list no List cached images, optional filter
docker_pull yes Pull an image by reference
docker_run yes Create and start a container (ports, env, runtime)
docker_compose_list no Registered compose projects and services
docker_compose_up / docker_compose_down yes Bring a registered stack up or down (remove_volumes on down also drops named volumes)

docker_run accepts a runtime — including trmnly for the built-in engine — so you can ask the agent to spin up a database with no Docker installed at all.