Tags: yuzlibugs/forkd
Tags
v0.5.2 — hugepage memfd + axum-server 0.8 + non-AI recipes (includes … …post-tag Dockerfile fix deeplethe#235 for ghcr.io)
v0.5.1 — guest kernel rebuild closes deeplethe#218 + deeplethe#225
docs: lead Quick start with forkd pull, plus v0.3.4 / doctor-screensh… …ot polish (deeplethe#165) * docs: audit sweep — sync stale v0.3.1/v0.3.2 refs to v0.3.4 Stale-content sweep after v0.3.4 ship + 4 v0.4 PoCs landed: - ROADMAP.md: bump 'Current release' from v0.3.1 to v0.3.4; add v0.4 RFC pointer; fix 'v0.2.x retro' → 'v0.4 retro' in speculative section. - README.md: '3 PoCs' → '4 PoCs' (Phase 4 restore PoC landed); extend phase-1 ship range to v0.3.0 → v0.3.4 with the multi-BRANCH fix note. - README-zh.md: mirror the EN updates — port the missing 'filesystem state, not just reasoning' section, refresh the v0.3.0 → v0.3.4 ship line, sync the recipes list to include jupyter-kernel / playwright-browser / postgres-fixture. - INTEGRATION-BOXLITE.md: extend ship range to v0.3.4, replace stale '14× aggregate' callout with the v0.3.4 17.6×/8.5× multi-BRANCH numbers + posix_fallocate fix narrative. - RESULTS-v0.3.md: embed v0.3.4-before-after.png chart alongside the 10-BRANCH numbers table. - Remove orphan docs/assets/wp-bench-demo.tape (vhs pivot to asciinema, .tape no longer used). Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * docs: embed forkd doctor screenshot (14 checks pass) into repo Previously this lived on imgur and was only referenced from outside the repo (HN post, etc.). Pulling it in-repo so: - README has a concrete visual for what 'forkd doctor passes' means - the screenshot survives independently of any third-party host - WebP keeps the asset small (82 KB vs 178 KB JPEG) Captured on the dev box: Linux 6.14, FC v1.12.0, 134 snapshots, 636 GiB free in the snapshot dir, daemon reachable on 127.0.0.1:8889. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * docs: lead Quick start with `forkd pull` recipe path Promote the Hub pull flow from "Fastest path — alternative section" to the recommended first-fork experience in both README.md and README-zh.md. The other quickstart sections (from-image, from-source) are reframed as alternatives for users who need custom recipes. The Chinese README previously omitted the Hub flow entirely; this PR adds the parallel `forkd pull deeplethe/langgraph-react` section and renumbers the trailing sections accordingly. End-to-end verified on the dev box: `forkd pull deeplethe/langgraph-react` downloads the 14.5 MiB pack in ~15 s, sha256 verifies, unpacks at tag `langgraph` ready for `forkd fork --tag langgraph -n 3`. Closes the M1.2 ROADMAP item "README quickstart rewritten to lead with `forkd pull`". --------- Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
hub: add deeplethe/playwright-browser v1 (Chromium warm-fork) (deeple… …the#167) Headless Chromium pre-launched with one about:blank tab and a line-based JSON-RPC command loop on stdin. Children inherit the warm renderer process via mmap CoW; sb.eval(<js>) routes into the loop and returns a result in ~10-80 ms vs the 2-3 s of cold-starting a headless Chromium container. Pack: 105.5 MiB compressed (2.00 GiB uncompressed, 19.4× zstd — Chromium memory has more entropy than pure Python). Memory: 2048 MiB (Chromium OOMs on the 512 MiB default). Base image: mcr.microsoft.com/playwright:v1.50.0-jammy Closes the M1.1 ROADMAP item "Hub-published playwright-browser pack ready for `forkd pull`". Release: https://github.com/deeplethe/forkd/releases/tag/hub-playwright-browser-v1 sha256: 811db4deddfdc4b07931e353b20370f7270946456ba8722d372ba239dbba3f86 Pull verified end-to-end on the dev box: download (~95 s at ~1 MiB/s on a residential link), sha256 matches, unpacks into a working snapshot tag.
docs: lead Quick start with forkd pull, plus v0.3.4 / doctor-screensh… …ot polish (deeplethe#165) * docs: audit sweep — sync stale v0.3.1/v0.3.2 refs to v0.3.4 Stale-content sweep after v0.3.4 ship + 4 v0.4 PoCs landed: - ROADMAP.md: bump 'Current release' from v0.3.1 to v0.3.4; add v0.4 RFC pointer; fix 'v0.2.x retro' → 'v0.4 retro' in speculative section. - README.md: '3 PoCs' → '4 PoCs' (Phase 4 restore PoC landed); extend phase-1 ship range to v0.3.0 → v0.3.4 with the multi-BRANCH fix note. - README-zh.md: mirror the EN updates — port the missing 'filesystem state, not just reasoning' section, refresh the v0.3.0 → v0.3.4 ship line, sync the recipes list to include jupyter-kernel / playwright-browser / postgres-fixture. - INTEGRATION-BOXLITE.md: extend ship range to v0.3.4, replace stale '14× aggregate' callout with the v0.3.4 17.6×/8.5× multi-BRANCH numbers + posix_fallocate fix narrative. - RESULTS-v0.3.md: embed v0.3.4-before-after.png chart alongside the 10-BRANCH numbers table. - Remove orphan docs/assets/wp-bench-demo.tape (vhs pivot to asciinema, .tape no longer used). Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * docs: embed forkd doctor screenshot (14 checks pass) into repo Previously this lived on imgur and was only referenced from outside the repo (HN post, etc.). Pulling it in-repo so: - README has a concrete visual for what 'forkd doctor passes' means - the screenshot survives independently of any third-party host - WebP keeps the asset small (82 KB vs 178 KB JPEG) Captured on the dev box: Linux 6.14, FC v1.12.0, 134 snapshots, 636 GiB free in the snapshot dir, daemon reachable on 127.0.0.1:8889. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]> * docs: lead Quick start with `forkd pull` recipe path Promote the Hub pull flow from "Fastest path — alternative section" to the recommended first-fork experience in both README.md and README-zh.md. The other quickstart sections (from-image, from-source) are reframed as alternatives for users who need custom recipes. The Chinese README previously omitted the Hub flow entirely; this PR adds the parallel `forkd pull deeplethe/langgraph-react` section and renumbers the trailing sections accordingly. End-to-end verified on the dev box: `forkd pull deeplethe/langgraph-react` downloads the 14.5 MiB pack in ~15 s, sha256 verifies, unpacks at tag `langgraph` ready for `forkd fork --tag langgraph -n 3`. Closes the M1.2 ROADMAP item "README quickstart rewritten to lead with `forkd pull`". --------- Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
hub: add deeplethe/postgres-fixture v1 (fork-per-test DB pattern) (de… …eplethe#168) PostgreSQL 16 with initdb complete and postmaster running before snapshot. Children fork into a ready-to-query database in ~10 ms, the isolated-DB-per-test shape from the README's production case shapes. Pack: 38.0 MiB compressed (1.00 GiB uncompressed, 26.9x zstd). Memory: 1024 MiB. Base image: postgres:16. Release: https://github.com/deeplethe/forkd/releases/tag/hub-postgres-fixture-v1 sha256: bba5e79aaab01830519b925a8ac9eebd0d21ecbecd9687408b18a0473324d27f Pull verified end-to-end on the dev box: 38 MiB download (~28 s), sha256 matches, unpacks into a working snapshot tag.
hub: add deeplethe/e2b-codeinterpreter v1 (E2B drop-in) (deeplethe#171) E2B code-interpreter image preloaded — Python + Node + Jupyter + many data/ML libs ready. Drop-in for the E2B sandbox API via forkd's Python SDK (from forkd import Sandbox). Pack: 21.6 MiB compressed (2.00 GiB uncompressed, 94.8x zstd). Memory: 2048 MiB. Base image: e2bdev/code-interpreter:latest. Release: https://github.com/deeplethe/forkd/releases/tag/hub-e2b-codeinterpreter-v1 sha256: 0ba779995b5b5c8fa41fb2868937e80ce7971348da786d9f72939631d974f39d
hub: add deeplethe/nodejs v1 (Node 22 generic JS base) (deeplethe#170) Node.js 22 slim runtime preloaded. Generic JS workload base — useful for npm-based agents, JS test runners, or any tool that needs a real Node process per child. Pack: 10.5 MiB compressed (512 MiB uncompressed, 49x zstd). Memory: 512 MiB. Base image: node:22-slim. Release: https://github.com/deeplethe/forkd/releases/tag/hub-nodejs-v1 sha256: 40e98bf012745fff8ae684b5c3956a1e33a6c2669dcd69e78011cbd830736abb
PreviousNext