Commit Graph
3 Commits
Author SHA1 Message Date
mhoennigandClaude Fable 5 de79210a7b Werkdock RFC 0002: docker-compatible surface in three levels
Level 1: docker-compatible CLI (verbs, flags, loud refusal of isolation
flags the filesystem-only contract cannot honor) — built in session B.
Level 2: OCI image pull, flattened to a rootfs — deferred, stdlib-doable.
Level 3: a daemon speaking the Docker Engine API subset Testcontainers
actually uses (Testcontainers never calls the CLI) — deferred, but the
CLI is built as a thin frontend over the same internal service from the
start. Records the port-mapping crux of host networking and the
unprivileged-netns escape hatch as a future RFC.

Step 21 session B and the werkdock README follow the docker-shaped
semantics: run takes an image, instances correspond to containers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-09-01 06:44:35 +02:00
mhoennigandClaude Fable 5 5544d4f99b Werkdock RFC 0001 accepted: Go it is
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-09-01 06:42:13 +02:00
mhoennigandClaude Fable 5 2abde3aec9 Werkdock RFC 0001: implementation language evaluation, proposing Go
The full five-way evaluation (bash, Python 3, Kotlin Native, Rust, Go)
with the numeric scoring, the Kotlin Native deep-dive, and the
own-namespaces-instead-of-bwrap analysis, ending in a concrete proposal:
Go, stdlib-only, one static binary, sandbox engine behind an interface
so bwrap can later be swapped for native namespaces.

Status proposed — the decision outcome is recorded once made.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-09-01 06:39:12 +02:00