What does HackerNews think of ignite?

Ignite a Firecracker microVM

Language: Go

#8 in Docker
> 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

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

> 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.

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

I have been following microvms and kubernetes lately. Nice thing about leveraging OCI is that you can use cri-o and orchestrate using kubernetes. I am pretty bullish on microvms.

Weavework has been doing quite some good stuff around OCI interface around microvms. Ignite[1] which is more robust and productize version of what is mentioned in this blog. Other projects that should be watched out for is kata containers [2]

[1] https://github.com/weaveworks/ignite

[2] https://gokulchandrapr.medium.com/kata-containers-on-kuberne...

Another Rust option is Firecracker, it manages micro VM but can be used for Docker, ala Fargate and https://github.com/weaveworks/ignite
I'm really excited to see where this goes in the community. There are some interesting projects using Firecracker such as Weave Ignite and firekube that I think could improve the security of Kubernetes. Also lightweight VMs are exciting in their own right.

https://github.com/weaveworks/ignite

https://github.com/weaveworks/wks-quickstart-firekube