Ah I see what you were referring too, yeh it’s been open source for something like 1.5 yr now. We actually had to do some special tasks (including a few patches to erlang GitHub - nanovms/erlang: patches for erlang to run on Nanos · GitHub ) to get Elixir working ops-examples/elixir at master · nanovms/ops-examples · GitHub and I’d imagine we have more work to do here as well to get a better/tighter integration.

Once upon a time there was LING (also known as Erlang on Xen), however this project seems pretty dead nowadays. There are other unikernels like Rump that have examples for Erlang. My problem with NanoVM is that it is closed source while there are other, open-source, projects that supports such approach.

In general from what I see the idea of unikernels pretty much died out (that is a shame) and waits for better times.

From the “high level” viewpoint the Nerves is the most unikernelish thing in the Erlang world right now.

And IMHO Erlang is perfect environment for unikernels runtime language, as it is mostly a operating system on it’s own, so removing one layer (“real” OS) wouldn’t harm 90% of Erlang applications while it would provide obvious benefits.

Note: I’m not an active elixir dev so there most definitely are probably better methods to do this but..

In this example you can see we actually use ‘mix release’: ops-examples/elixir/02-phoenix at master · nanovms/ops-examples · GitHub . Elixir makes use of quite a few wrapping scripts to setup paths/env vars and that’s the most challenging aspect imo of running it under nanos as you need to declare all of that up front. I think there is definitely room here for extra/better tooling.

Other than that I wouldn’t say there are huge issues but yeh I think it would be good to try and get some newer releases cut. Let me know if you want to take a quick stab at it or if you run into any issues happy to take a look.