“Firecracker is an open source virtualization technology that is purpose-built for creating and managing secure, multi-tenant container and function-based services that provide serverless operational models. Firecracker runs workloads in lightweight virtual machines, called microVMs, which combine the security and isolation properties provided by hardware virtualization technology with the speed and flexibility of containers.”
Happy to see the kernel init parameters fix land! For context, I used firecracker (very successfully) in a CTF, driven via a Discord bot.<p>One of the challenges I tried to build was one where a player would get access to the kernel commandline with the goal being that they should hack their way around the environment to get access to an encrypted disk. Unfortunately, that was when I get the now fixed bug[1].<p>[1] <a href="https://github.com/firecracker-microvm/firecracker/issues/2709" rel="nofollow">https://github.com/firecracker-microvm/firecracker/issues/27...</a>
Hey so how is are the virtual machines different from KVM? I still don't know when I should consider using firecrackervm in my homelab or my business.
Sorry for a meta question but is the "Show HN" tag correctly applied? I tried to check if the poster is a developer of Firecracker, but unless that their contributions were pre-GitHub, I don't think that the tag qualifies.