Firecracker

“things like Firecracker are a better bet from a security standpoint”

“Firecracker has a long track record but has a lot of knobs and tunings to get the security right.”

“The whole point of Firecracker over normal VM solutions is that "booting an OS" takes milliseconds.”

“Having to boot an entire OS inside a VM is a step backwards compared to containerisation”

“which seems to hold them off long enough for me to see an agent going rogue and intervening”

“Firecracker I can trust to be secure because it's 70k lines of human audited Rust.”

“it has no support for many things, eg host filesystem mounting in the guest”

“Firecracker mounts very few host systems into the VM, exposing minimal host code to malicious guests.”

“Firecracker only allows block devices, so re-attaching an agents disk workspace requires a custom storage interface”

“We wanted a cloud computer for our agent that would be as close to a metal box as possible.”

“Amazon is actually pretty good about open sourcing core technologies like that. Firecracker is a big one.”

“the conclusion to use firecracker or gvisor is obvious, that's what they were made for”

“the vulnerability it found in Firecracker required incredible effort and positioning”

“you can't just `apt install postgres` on firecracker, it needs to get baked into the image first”

“the fact that one can run scalable sandboxes for untrusted code on Kubernetes making use of Firecracker and CoW is pretty neat”

“Firecracker is an exceptional piece of code and it's carried me far”

“Firecracker just has a ReSTful unix socket with a defined API and launches KVM vms with limited options.”

“Firecracker has more tooling for the orchestration layer that manages many sandboxes at once.”

“try lightweight VMs like Firecracker, or paravirtualization (like VM but with a shared kernel). Those solutions are made for server use”

“That's why we moved to a fully in-house solution with Firecracker and auto-scaling on EC2”

“It is basic and it works. We have not had any issues since deployed.”

“firecracker is an obvious place to start because it offers best-in-class support fast cold starts and hard isolation”

“Firecracker and gVisor don't at all feel like "libraries that install cleanly."”

“Firecracker is extremely hardened, so I wouldn't worry about Lambda.”

“You're likely to experience operational + setup hiccups to use it in production.”

“I worked with firecracker a lot back in the day and realized it was a pain to use.”

“really strong sandboxing solutions, such as gvisor or firecracker, do a really good job of having very little attack surface”

“Exploitation of Firecracker is, from my view, extremely difficult.”

“we had a very long onboarding doc to dev on firecracker for containers”

“most uncommon emulators lag behind on the boring but needed patches compared to QEMU or Firecracker”

“launch Firecracker microvm with its own kernel, so you get hardware-level isolation”

“Firecracker is also insanely safe - 3 CVEs ever, and IMO none are exploitable.”

“We recently built our own sandbox environment backed by firecracker and go. It works great.”

“The non-escalating envelope approach in Firecracker is a great way to handle agent drift.”

“The entire "cloud" layer is Firecracker + Btrfs reflinks for instant copy-on-write cloning.”

“It strips down the kernel to the bare minimum, so you get VM-level isolation with millisecond boot times”

“Firecracker can solve the kind of problems where you want more isolation than Docker provides, and it's pretty performant.”

“firecracker is also not super useful as afaik GPU passthrough is not ideal/working”

“Firecracker is also awkward because GPU support is pretty hard / impossible.”

“Last I explored that it still felt pretty rough. (on UX not tech quality)”