Future plans for the public Firecracker fork / self-host source builds?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 438
- PR merge metrics
- No merged PRs in 30d
Description
Hi team, thanks for open-sourcing the infra 🙏
I'm self-hosting and would like to build the whole stack from source, including Firecracker.
I noticed the customized Firecracker fork (e2b-dev/firecracker) is now archived, and fc-versions/build.sh defaults to e2b-dev/e2b-firecracker, which isn't publicly accessible.
A few questions on future plans:
- Is there a recommended public source for building a compatible Firecracker going forward, or is downloading the prebuilt binaries the intended path for self-hosters?
- Now that the fork is archived, will the Firecracker source (or prebuilt binaries) keep being published publicly for future versions?
- Any guidance on how self-hosters should track the fork against upstream over time?
Totally understand if this isn't a priority. Thanks for the great work!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading fc-versions/build.sh and checking the archived e2b-dev/firecracker fork and the inaccessible e2b-dev/e2b-firecracker reference. Document the supported public source or binary path for self-hosters, future publication expectations, and how to track the fork against upstream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- infrastructure
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100