SUsurajrmal·Dec 6, 2023
According to their own FAQ it is indeed: https://github.com/firecracker-microvm/firecracker/blob/main...
In Virtual Machine as a core Android Primitivefirecracker-microvm
firecracker
Rust2018–2026
firecracker-microvm / firecracker
firecracker
Secure and fast microVMs for serverless computing.
84Distinct people
102Mentions
0Explicit recommenders
38KGitHub stars
What to know before exploring
What it is
Secure and fast microVMs for serverless computing.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- cloud-hypervisor/cloud-hypervisor · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year102 dated mentions
Observed mentions: 2018-11-27 05:00:35 UTC to 2026-09-30 23:40:36 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 14 | 0 | 14 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 27 | 4 | 23 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 10 | 2 | 8 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 15 | 0 | 15 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 7 | 3 | 4 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 9 | 0 | 9 |
What Hacker News says
10 sourcesVMM's such as firecracker and cloud-hypervisor translate between vsock and UDS. [1]
In recent kernel versions, sockmap also has vsock translation: <https://github.com/torvalds/linux/commit/5a8c8b72f65f6b80b52...>
This allows for a sort of UDS "transparency" between guest and host. When the host is connecting to a guest, the use of a multiplexer UDS is required. [1]
[1] <https://github.com/firecracker-microvm/firecracker/blob/main...>
In Unix Domain Sockets vs Loopback TCP Sockets (2014)Hey HN,
We've been building cloud for AI agents/copilots/AI apps. One of the first products that we're launching are AI Playgrounds. It's essentially a sandboxed VM (Firecracker [0]) where your agent can freely run code, use filesystem, use headless browser, and more. Every playground has also it's own URL. So for example you can have your agent start a webapp, let the agent work on it inside the playground, and because the playground has URL, the user can see all of the changes.
We've seen that it's especially useful for coding copilots and agents. They can easily run linters, formatters, or debug code and feed all this information back to LLM to make the next iteration better. Our short-term goal is to offer coding agents/copilots all of the tooling that human developers get in their coding editors. And have all of this happen in a secu
Read the rest
re sandboxed environment that people will eventually be able to self-host it.
You don't need to manage any infrastructure. You just call a single line of code with our SDK and we spin up a cloud playground in a few hundred ms for your AI app.
We have parts of our product open source here https://github.com/e2b-dev and are thinking of actually open-sourcing the whole infrastructure and make it really easy to 1-click deploy for anyone. One of the reasons we haven't done that is how much tooling we had to build on top Firecrackers and how much specialized environment they need. Which makes it a bit of challenge to offer great DX.
Happy to answer more questions!
[0] https://github.com/firecracker-microvm/firecracker
If you're interested in learning more about that, check out our NSDI'20 paper on how we chose this direction (https://www.usenix.org/conference/nsdi20/presentation/agache) and the Firecracker source and docs (https://github.com/firecracker-microvm/firecracker).
Thanks to KVM, and to the minimal hardware support (no PCI, no ACPI, etc), Firecracker's source is rather simple and even relatively readable for non-experts.
In FreeBSD on FirecrackerAdd FreeBSD kernel+rootfs build instructions · firecracker-microvm/firecracker
2 points · Open discussionGeneralized oversubscription like that is very challenging if not impossible to do securely, since you want to keep workloads isolated to single tenant numa nodes.
E.g. using the firecracker jailer: https://github.com/firecracker-microvm/firecracker/blob/main...
In We replaced Firecracker with QEMU"Firecracker's RAM footprint starts low, but once a workload inside allocates RAM, Firecracker will never return it to the host system."
Firecracker has a balloon device you can inflate (ie: acquire as much memory inside the VM as possible) and then deflate... returning the memory to the host. You can do this while the VM is running.
https://github.com/firecracker-microvm/firecracker/blob/main...
In We replaced Firecracker with QEMUVery few things in those companies are being written in Rust, and half of those projects chose Rust around ideological reasons rather than technical, with plenty of 'unsafe' thrown in for performance reasons
https://github.com/firecracker-microvm/firecracker/search?q=...
The fact that 'unsafe' even exists in Rust means it's no better than C with some macros.
Don't get me wrong, Rust has it's place, like all the other languages that came about for various reasons, but it's not going to gain wide adoption.
Future of programming consists of 2 languages - something like C that has a small instruction set for adopting to new hardware, and something that is very high level, higher than Python with LLM in the background. Everything in the middle is fodder.
In Neverflow: C macros that guard against buffer overflowsIn a phrase: try, try again.
Pick a simple bug, dive in and send a fix. Repeat. Level up the difficulty. Repeat.
They have labeled some bugs as good for first contributions:
https://github.com/firecracker-microvm/firecracker/issues?q=...
In Ask HN: How do you start contributing to big OS projects?Ask HN: How do you start contributing to big OS projects?
I'm a junior software engineer, I've been programming for at least 10 years, wayyy before college. I am working on a lot of interesting side projects but I've never really jumped into a big open source project.
I recently wanted to apply for a position in the Firecracker [0] team because the project really interest me and gets me excited, so I thought that contributing to it would increase my chances of getting an interview for that position.
The problem I'm facing right now is that the project feels very intimidating, it's giant and I don't know where to start/how to lay down a strategy to slowly get myself comfortable with it.
Maybe I started with a project that is too complex and definitely requires much more knowledge that I currently have, but I would really love to know other stories and approaches that the HN community have to shar
Read the rest
e on open source contributions other than the classic "start with the good first issue".
[0]: https://github.com/firecracker-microvm/firecracker