containers
Skill9 starsChanged 4 days agoMITView on GitHub
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.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- th3r-dev/th3-skillstheir own version, first seen Nov 16, 2026
- seayniclabs/homelab-infra-mcptheir own version, first seen Nov 8, 2026
- microsoft/azure-dev-toolstheir own version, first seen Oct 25, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- BrendenKennedy/claude-for-ai-platformstheir own version, first seen Oct 13, 2026
- sentineldesk/agenttheir own version, first seen Aug 24, 2026
Used with
Projects with it also use observability.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- nimadorostkar/Claude-Skills-collection★ 37same name
- microsoft/azure-dev-tools★ 11same name
- zllovesuki/cloudflare-agent-skills★ 9same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- th3r-dev/th3-skills★ 2same name
- BrendenKennedy/claude-for-ai-platforms★ 1same name
- seayniclabs/homelab-infra-mcp★ 0same name
- sentineldesk/agent★ 0same name
- weiweimhy/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- app-testingSkill
- claude-panelSkill
- commands-settingsSkill
- debuggerSkill
- files-git-searchSkill
- i18nSkill
- lspSkill
- main-ipcSkill
- main-processesSkill
- packaging-releaseSkill
- renderer-componentsSkill
- renderer-editorSkill
- renderer-storeSkill
- renderer-stylesSkill
- renderer-terminalSkill
- workspacesSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Every docker process is spawned as a process group and owned by a view (or by the shared ps cache).
- Very specific: line 23
EVERY docker process is an own process group (process/spawnGroup.ts, killed on timeout, view navigate/destroy and will-quit via …
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.tsis wiring only (channels, validation, delegation). The docker CLI runs from the user-onlydocker.path(empty =dockerof the login-shell PATH,docker/executable.ts;.cmd/.batrejected on Windows). Modules indocker/:run.ts(specFor,spawnLive,run, theoneShotsregistry),viewState.ts(per-viewViewState: lastps, stats/logs streams,logSeq;stopStatsOf/stopLogsOf; theonViewResetstop),statsStream.ts/logsStream.ts(classes withstart/stop, injectedspawn, tested withtesting/fakeGroupProcess.tsand fake timers),streams.ts(startStats,followLogs: spec +send+ view state),ps.ts(fetchPs, sharedpsCache),commands.ts(info, actions, compose, inspect, investigation prompt),composeTarget.ts(members → validated working dir and files),exec.ts(dockerExecCommand, terminal source).docker/**never imports fromclaude/**: the executable comes fromenv/executable.tsresolveExecutable, the env fromenv/childEnv.tsbuildChildEnvand the PATH fromenv/loginShell.tseffectivePath().- Stream lines (
logs -f,stats) are split withutil/lineSplitter.tscreateLineSplitter(CRLF aware, capped line). - EVERY docker process is an own process group (
process/spawnGroup.ts, killed on timeout, view navigate/destroy andwill-quitviakillAllSpawnedGroups): continuous ones (stats,logs -f) throughspawnLive, one-shot commands (run: compose up, actions, inspect…) throughrunCollect(process/runCollect.ts) withgroup: trueandowner: oneShots.scope(sender);runonly classifies the result intoDockerError. One-shots are tracked in the view (oneShotsregistry inrun.ts), killed on view reset and block hibernation (eviction guarddocker) while running, except the sharedps(psCache), which belongs to no view;statsandlogs -fare per view and only while the screen / the detail is open (logSeqis bumped even before the follow spawns, so a stop duringspecFornever leaves an orphan). logs -fbatches lines perLOGS_BATCH_MStick (at mostLOGS_BATCH_MAXper tick; the excess waits for the next tick, nothing is dropped). AboveLOGS_HIGH_WATERMARKqueued lines both pipes are paused (a main-side throughput cap, there is no renderer ack) until the queue falls toLOGS_LOW_WATERMARK; on exit the whole queue is delivered beforedocker:logsEnd.- Stdout over
MAX_BUFFER(16 MB,runCollectmaxBufferwith the defaultonOverflow: 'kill') kills the process and fails withDockerErrorreasonoutputTooLarge; 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 lastps) 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
infowith an emptyServerVersion(parseInfo.ts→daemonDown); errors carry theirDockerInfoError(DockerError), never reclassify the translated message. - Docker output in the Claude prompt is untrusted:
investigation.tsdelimited/truncated blocks, env values never leave main, secrets in the command masked (maskSecrets.ts). - Renderer: the takeover is
screen: 'workbench' | 'containers'(NOTview, never in the session); everything else stays mounted and hidden (.workbench.takeover), toasts portal tobody, Claude sessions don't count as seen while on containers, andexecuteCommandleaves the screen first for editor/tab commands (⌘W only leaves it; theregisterOverlayPolicyindockerActions.ts, registered bystartDockerReactions). - E2E use
e2e/fixtures/fake-docker.mjs(state inWALPH_FAKE_DOCKER_STATE,.calls.jsonl/.pidsbeside it).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

