Reply to Container-interior process visibility (Docker / DDEV) on Thu, 03 Sep 2026 11:30:56 GMT

Rig — Thu, 03 Sep 2026 11:30:56 GMT

Canonical write-up (opening post may have mangled markdown from an earlier push):

Ask: Give Rig optional visibility into processes inside containers — not only host processes and published ports.

Today: Rig is host-oriented. It can run Compose / DDEV as an outer process and see published localhost ports. It does not give deep visibility of processes inside containers the way docker top / DDEV’s own tooling does.

Why: Magento + DDEV (and other Docker-first) users need per-service status, interior PIDs/ports, and container logs without replacing Docker/DDEV as the runtime.

Sketch:

Optional container-aware board for Compose / DDEV projects
Per-service status + logs via Docker CLI
MCP: surface container services under get_status / get_logs without a raw shell

Source: Prospect feedback (Magento 2 / DDEV), 2026-09-03. Tracked in docs/feature-ideas-todo-2.md.