Problem Statement
The Containers screen could list Docker containers and Exec into them (0.1.12) and handle Kubernetes logs + port-forward (0.1.34), but the Docker side stopped at a read-only list. DevOps/SRE users managing containers on a host had to drop to a raw shell for everyday actions — viewing logs, restarting a crashed container, or bringing a Compose stack up/down.
Proposed Solution
Finish the Docker container story in the Containers screen:
- Docker tab — list all containers (
docker ps -a), per-container Stop / Start / Restart, one-click Exec into a new SSH tab, and an inline follow-mode log viewer (docker logs -f) with auto-scroll and a line cap.
- Compose tab — discover Compose v2 stacks (
docker compose ls + a find sweep, plus manual path add), per-stack Up / Down, per-service Start / Stop with replica counts, and per-service follow-mode logs.
- 3-tab layout: Docker | Compose | Kubernetes, each gated on its runtime with an install/permission hint.
Alternatives Considered
- Shelling out manually — defeats the point of an integrated panel.
- A single combined tab — Compose discovery and per-service controls don't map cleanly onto the flat container list, so separate tabs read better.
Additional Context
- Spec:
docs/superpowers/specs/2026-06-18-docker-panel-completion-design.md
- Plan:
docs/superpowers/plans/2026-06-18-docker-panel-completion.md
- Docker Compose v1 (
docker-compose) is out of scope; discovery degrades to find-only.
Problem Statement
The Containers screen could list Docker containers and
Execinto them (0.1.12) and handle Kubernetes logs + port-forward (0.1.34), but the Docker side stopped at a read-only list. DevOps/SRE users managing containers on a host had to drop to a raw shell for everyday actions — viewing logs, restarting a crashed container, or bringing a Compose stack up/down.Proposed Solution
Finish the Docker container story in the Containers screen:
docker ps -a), per-container Stop / Start / Restart, one-click Exec into a new SSH tab, and an inline follow-mode log viewer (docker logs -f) with auto-scroll and a line cap.docker compose ls+ afindsweep, plus manual path add), per-stack Up / Down, per-service Start / Stop with replica counts, and per-service follow-mode logs.Alternatives Considered
Additional Context
docs/superpowers/specs/2026-06-18-docker-panel-completion-design.mddocs/superpowers/plans/2026-06-18-docker-panel-completion.mddocker-compose) is out of scope; discovery degrades to find-only.