ignite

> I will say that I prefer running LXD on NixOS hosts where it isn't packaged as a snap. Hopefully canonical doesn't somehow break that. Same, though it seems this acquisition is mainly about snaps, so we'll see. I wish Nix would package Kata, a hybrid of containers and VMs. I would migrate to that from LXD. https://katacontainers.io/ It does have Firecracker and Ignite though, which I haven't tested but probably also suffice. https://firecracker-microvm.github.io/ https://github.com/weaveworks/ignite

Not a drop-in replacement: the OCI image entry point is not automatically executed. Issue opened in 2021: https://github.com/weaveworks/ignite/issues/874

https://github.com/weaveworks/ignite ?

> If it's not hard to name a thing that Firecracker makes difficult for a serverside workload, could you... name one? I already did that with live migration. But ok. Encrypted storage: https://github.com/firecracker-microvm/firecracker/issues/65...: WONTFIX The answer given is appropriate for firecracker use cases but insufficient otherwise. I'm not anti-firecracker; it's the right choice for many things. Just not all things. The sort of VM I want orchestrated has encrypted (by contract) multi-pathed network block devices to encrypted storage volumes. 3-10 per tenant. This is trivial for a full-featured kernel; multi-path just works, encryption just works. VLAN: https://github.com/weaveworks/ignite/issues/810: Open. Maybe one day. Again, trivial for a full-featured Linux kernel. Has been for ages. I think you're missing the point.

This is a great idea and something I would love to use, but it's a lot less docker compatible and user friendly than it may seem. For instance there is no way to automatically run the image's specified command, effectively leaving you with a dead VM: https://github.com/weaveworks/ignite/issues/874. You also simply can not share directories with the host (out of scope for Firecracker). microVMs for running containers are definitely a great idea; another project aiming to do it (a little differently) is Kata Containers. It has a lot more industry support, can also run on Firecracker (though QEMU microVMs are just as good) and can (theoretically, I haven't gotten it to work) interact with many container runtimes that are not Docker (the focus appears to be on Kubernetes). While more powerful, Kata Containers are also much, much more complica

I skimmed the paper, but the premise makes sense in some scenarios. I don't think unikernels have quite taken off as they were hyped a few years ago, but in general, micro VMs are quite more usable nowadays. I recently gave Firecracker a try, via the friendlier interface of Ignite[1], and was pleasantly surprised how quick it was to start a VM from a Docker image, and how little resources it used. The UX is pretty much on par with Docker, yet gives much more flexibility, control, and of course, security. I wish there was a competitor to QubesOS that uses KVM, and is a bit friendlier and more polished. Is there such a distro? [1]: https://github.com/weaveworks/ignite

https://github.com/weaveworks/ignite can apparently do this. It looks exciting!

> So from that perspective, when I've peeked at firecracker, kata containers, etc, the "small dev dx" isn't quite there yet, or maybe never will get there since the players target other spaces (aws, fly.io, etc). Stuff like a way to share volumes isn't supported, etc. Personally I find Dockers architecture a bit distasteful and Podmans tooling isn't quite there yet (but very close). This is pretty much me and my homelab. I haven't visited it in a while, but Weave Ignite might be of interest here. https://github.com/weaveworks/ignite

I have been using Weave Ignite [1] recently to run Firecracker micro vm(s) instead of containers for a multitude of tasks! 1. https://github.com/weaveworks/ignite

Depends, is your code being served to the internet? If it is I would definitely consider firecracker but if its just internal it probably won't matter a whole lot. Not sure about the overhead of docker compared with firecracker though, so there may be advantages there either way. There's also ignite which works with firecracker: https://github.com/weaveworks/ignite

Take a look at Weaveworks Ignite for an open source tool for running Firecracker VMs from container images: https://github.com/weaveworks/ignite And of course AWS Fargate and Lambda use this tech under the hood transparently, so that's always an option if you don't want to host and operate it yourself.

A couple more: https://github.com/containers/krunvm https://github.com/weaveworks/ignite

Kubevirt is just another way to showcase how flexible kubernetes scheduling is via crio. One of the things I am excited about is microvm orchestration with kubernetes. Weavework has a really cool project in that realm [1]. [1] https://github.com/weaveworks/ignite

Have you looked into Weaveworks Ignite? https://github.com/weaveworks/ignite