docs(v0.4): vendor firecracker, document fork strategy#185
Merged
Conversation
Adds docs/VENDORED-FIRECRACKER.md explaining why forkd vendors a patched Firecracker (the mem_backend.shared MAP_SHARED option that v0.4's live-fork needs) and where the fork lives: https://github.com/deeplethe/firecracker branch: forkd-v0.4-mem-backend-shared Also flips DESIGN-v0.4-PHASE3-SPIKE.md's status banner from SPIKE to RESOLVED, noting we picked Option B (vendor) + Option A (upstream proposal, filed at firecracker-microvm/firecracker#5912). The vendor path lets Phases 5a-9 proceed regardless of upstream timing. No code change in this PR — just the strategic decision + how to build the patched binary.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the decision to vendor a patched Firecracker for v0.4 (rather than wait on the upstream proposal at firecracker-microvm/firecracker#5912 which is following the standard 30-90 day Feature Request SLA).
New file
docs/VENDORED-FIRECRACKER.md— what / why / where / how:deeplethe/firecracker:forkd-v0.4-mem-backend-shared, one commit (b30f1ba) — the proposal's 33-line diff applied verbatim.tools/devtool build --release)./proc/<pid>/mapsrw-svsrw-ptest).Updated
DESIGN-v0.4-PHASE3-SPIKE.md— flips the status banner from SPIKE to RESOLVED. The original options analysis (A through E) is preserved below the banner as the decision trail.No code in this PR
Just the strategic decision + how to build the patched binary. The forkd-side integration (Phase 5a —
memfd_createin the spawn path) lands separately.