containers
/containers
Containers screen patterns: docker CLI owned per view (ipc/docker.ts, src/main/docker), process groups and one-shot tracking, id/compose validation, untrusted docker output sent to Claude, the containers takeover in the renderer and the fake docker for E2E. Use when creating or reviewing anything in src/main/docker, ipc/docker.ts or the containers screen.
- Author
- filipe-campos ↗
- Repository
- walph ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Containers screen patterns: docker CLI owned per view (ipc/docker.ts, src/main/docker), process groups and one-shot tracking, id/compose validation, untrusted docker output sent to Claude, the containers takeover in the renderer and the fake docker for E2E. Use when creating or reviewing anything in src/main/docker, ipc/docker.ts or the containers screen.
Original author description
Containers screen patterns: docker CLI owned per view (ipc/docker.ts, src/main/docker), process groups and one-shot tracking, id/compose validation, untrusted docker output sent to Claude, the containers takeover in the renderer and the fake docker for E2E. Use when creating or reviewing anything in src/main/docker, ipc/docker.ts or the containers screen.
How it works
- Containers
SKILL.md preview
--- name: containers description: Containers screen patterns: docker CLI owned per view (ipc/docker.ts, src/main/docker), process groups and one-shot tracking, id/compose validation, untrusted docker output sent to Claude, the containers takeover in the renderer and the fake docker for E2E. Use when creating or reviewing anything in src/main/docker, ipc/docker.ts or the containers screen. --- # Containers (`src/main/docker`, `ipc/docker.ts`) Every docker process is spawned as a process group and owned by a view (or by the shared `ps` cache). ## Containers - `ipc/docker.ts` is wiring only (channels, validation, delegation). The docker CLI runs from the user-only `docker.path` (empty = `docker` of the login-shell PATH, `docker/executable.ts`; `.cmd`/`.bat` rejected on Windows). Modules in `docker/`: `run.ts` (`specFor`, `spawnLive`, `run`, the `oneShots` registry), `viewState.ts` (per-view `ViewState`: last `ps`, stats/logs streams, `logSeq`; `stopStatsOf`/`stopLogsOf`; the `onViewReset` stop), `statsStream.ts` / `logsStream.ts` (classes with `start`/`stop`, injected `spawn`, tested with `testing/fakeGroupProcess.ts` and fake timers), `streams.ts` (`startStats`, `followLogs`: spec + `send` + view state), `ps.ts` (`fetchPs`, shared `psCache`), `commands.ts` (info, actions, compose, inspect, investigation prompt), `composeTarget.ts` (members → validated working dir and files), `exec.ts` (`dockerExecCommand`, terminal source). - `docker/**` never imports from `claude/**`: the executable comes from `env/executable.ts` `resolveExecutable`, the env from `env/childEnv.ts` `buildChildEnv` and the PATH from `env/loginShell.ts` `effectivePath()`. - Stream lines (`logs -f`, `stats`) are split with `util/lineSplitter.ts` `createLineSplitter` (CRLF aware, capped line). - EVERY docker process is an own process group (`process/spawnGroup.ts`, killed on timeout, view navigate/destroy and `will-quit` via `killAllSpawnedGroups`): continuous ones (`stats`, `logs -f`) through `spawnLive`, one-shot commands (`run`: compose up, actions, inspect…) through `runCollect` (`process/runCollect.ts`) with `group: true` and `owner: oneShots.scope(sender)`; `run` only classifies the result into `DockerError`. One-shots are tracked in the view (`oneShots` registry in `run.ts`), killed on view reset and block hibernation (eviction guard `docker`) while running, except the shared `ps` (`psCache`), which belongs to no view; `stats` and `logs -f` are per view and only while the screen / the detail is open (`logSeq` is bumped even before the follow spawns, so a stop during `specFor` never leaves an orphan). - `logs -f` batches lines per `LOGS_BATCH_MS` tick (at most `LOGS_BATCH_MAX` per tick; the excess waits for the next tick, nothing is dropped). Above `LOGS_HIGH_WATERMARK` queued lines both pipes are paused (a main-side throughput cap, there is no renderer ack) until the queue falls to `LOGS_LOW_WATERMARK`; on exit the whole queue is delivered before `docker:logsEnd`. - Stdout over `MAX_BUFFER` (16 MB, `runCollect` `maxBuffer` with the default `onOverflow: 'kill'`) kills the process and fails with `DockerError` reason `outputTooLarge`; it is never truncated silently. Stderr keeps only a bounded tail (verbose compose builds are not a failure). - Ids from the renderer pass `resolveContainerRef` (12–64 hex or a name from that view's last `ps`) and always go after `--`; compose dirs/files come only from the container labels and must exist. - Docker 27 with the daemon stopped exits 0 on `info` with an empty `ServerVersion` (`parseInfo.ts` → `daemonDown`); errors carry their `DockerInfoError` (`DockerError`), never reclassify the translated message. - Docker output in the Claude prompt is untrusted: `investigation.ts` delimited/truncated blocks, env values never leave main, secrets in the command masked (`maskSecrets.ts`). - Renderer: the takeover is `screen: 'workbench' | 'containers'` (NOT `view`, never in the session); everything else stays mounted and hidden (`.workbench.takeover`), toasts portal to `body`, Claude sessions don't count as seen while on containers, and `executeCommand` leaves the screen first for editor/tab commands (⌘W only leaves it; the `registerOverlayPolicy` in `dockerActions.ts`, registered by `startDockerReactions`). - E2E use `e2e/fixtures/fake-docker.mjs` (state in `WALPH_FAKE_DOCKER_STATE`, `.calls.jsonl`/`.pids` beside it).
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · filipe-campos/walph | 90 | MIT |
| xobotyi/cc-foundry | 100 | MIT |
| nimadorostkar/Claude-Skills-collection | 100 | MIT |
| lynricsy/hyperskills | 100 | MIT |
| soneta/soneta-erp-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version ca5346122d60 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100main-ipc
IPC patterns between the Electron main process and the renderer (typed contract in src/shared/types/<domain>.ts, runtime channel spec in src/shared/ipcSpec.ts, ipcMain handlers in src/main/ipc, generated contextBridge in src/preload, consumption in the store). Use when creating… - 90workspaces
Window and workspace patterns: BaseWindow + one WebContentsView per workspace (src/main/window), the folder owned by main per view, sessions and windows.json, the close/quit guard, dormant and hibernated views, viewActive gating and the welcome screen (recent folders, open many,… - 95docker-helper
Complete Docker operations via CLI - containers, images, networks, volumes, and compose When user mentions Docker, containers, docker commands, Dockerfile, images, docker-compose, or container registry - 95skill-148
Expert guidance for Development Containers (devcontainers) in VS Code. Create, configure, and manage devcontainer.json files, use Templates and Features, integrate with Docker/Docker Compose, and troubleshoot common issues. Use when working with devcontainers, containerized… - 100docker-patterns
Provides Docker and Docker Compose patterns including multi-stage builds, networking, volumes, and production configurations. Use when working with Dockerfile or docker-compose.yml, or when the user mentions Docker, containers, or containerization. - 95docker-cheatsheet
Use when the user needs Docker commands: building and running containers, images, volumes, networks, Docker Compose, logs, exec, port mapping, cleanup, and troubleshooting containers that will not start or keep restarting.