Show HN: Firecracker Lab – Build a microVM from a container image
github.com
github.com
Edit: I've added a link for a live-stream I'll be doing with Richard Case from Weaveworks on use-cases, differences vs. containers and legacy VMs - and a number of demos.
If you're only running your own code, is Firecracker better in some way than just using docker?
There's also ignite which works with firecracker: https://github.com/weaveworks/ignite
If you're more interested in integrating with Firecracker into your own systems - come to the session because I'm covering this in detail.
Weaveworks is now working on a new tool to create K8s clusters where each node is a microVM - Richard Case will be doing a demo of that, and it's super fast. It's for a Telco customer they have, so it's a real use-case, not just shiny tech, so should score extra points, right?
I think one day we will look back how insane it is that our programs are not isolated. Why does every program I run need access to my SSH keys?
So if you have workflows which that you're struggling to make work in a container, without root, a microVM gives you a full environment, where you can do whatever you want.
Of course, we are covering all this in the live-stream, see the link at the end of the repo!
The story with firecracker is that it’s a great tool for rolling out very lightweight vms. It’s for sure production ready. What’s missing is a nicely packaged docker-like set of tools which do not require a bunch of different technologies being glued together. The biggest one being for sure integrated overlay cni…
I’ve written a bit on firecracker before: https://gruchalski.com/tags/firecracker/.
Firecracker was developed at Amazon Web Services to accelerate the speed and efficiency of services like AWS Lambda and AWS Fargate. Firecracker is open sourced under Apache version 2.0.
To read more about Firecracker, check out https://firecracker-microvm.io.