unik

And on that note, I just found this list of UniKernel projects: http://unikernel.org/projects/ I have especially had hopes for the UniK [1] project, as it was/is written in Go AFAIK. I see now it incorporates work from the Mirage project as well. Not sure what is the status of this project anymore though. [1] https://github.com/solo-io/unik

Not on ESXI, but as unikernels, sure, https://github.com/solo-io/unik https://hermitcore.org/ https://github.com/icexin/eggos https://nanovms.com/ "Pure Go Unikernels - go metal with TamaGo" https://www.youtube.com/watch?v=aOEl5BCfHv0

> Why not? Most people won't spend the time to learn OS/distro building. I don’t know how good they are and have never used any, but there’s tooling for building the ultimate stripped down kernel, unikernels (https://en.wikipedia.org/wiki/Unikernel) A quick Google gives me https://nanovms.com/, https://github.com/solo-io/unik and https://github.com/rumpkernel/rumprun. A disadvantage of such a stripped down system is that debugging such a system can be difficult. For example, if there’s only one process, you can’t open a shell to look around on a misbehaving system.

Crazy idea that I'm sure isn't an original thought: instead of adapting the languages to deal with abstracting the idiosyncrasies of each OS, change the OSes to expose a universal API to make everything else lighter. I guess that's also kinda Docker or QEMU or V8, but also https://github.com/solo-io/unik if you think about it differently. In other words: hey, Lisp Machines were an excellent idea back then, but they still are. Maybe someday we'll have a V8 co-processor. More fun reading: https://lobste.rs/s/2poahh/what_i_could_not_undiscover_about

The HN conversations around unikernels suggest that they're not ready for production yet [0] but feel free to set that record straight. In the meantime, a handful of organisations/individuals seem to be working on becoming "Docker for unikernels". That's probably an unfair description, but they're aiming to produce tools for building and managing unikernels: Unikraft [1], NanoVMs/Nanos [2], Unik [3]. Other orgs are producing unikernel-based OSs and VMs [4]. What is your toolset for building and managing unikernels? What have you learned? Bonus question: is Unik dead? [5] [0] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... [1] https://unikraft.org/ [2] https://github.com/nanovms/nanos [3] https://github.com/solo-io/unik/ [4] http://unikernel.org/projects/ [5] https://github.com/solo-io/unik/issues/172

Absolutely terrible naming collision with another Go Unikernel project: https://github.com/solo-io/unik

Looks nice, thank. There is github.com/solo-io/unik as well. Had no time to check it out yet.

Related: Anyone have experience with Go and Unikernels? Saw a dead discussion a week ago on unik (https://github.com/solo-io/unik) For security purposes, the idea of a unikernel rather than a container has been very interesting. Wanted to use them in a test soon.

for anyone interested in running Go apps as Unikernels, I suggest checking out https://github.com/solo-io/unik disclosure: I'm one of the authors

solo.io | Cambridge, MA or remote | Full Time | https://www.solo.io solo is an exciting new startup (https://trueventures.com/solo-future-of-cloud/, https://www.solo.io/single-post/2017/11/01/Solo’s-seed-fundi...), currently we are hiring: * systems engineer (https://www.solo.io/system-software-engineer) * UX Engineer (https://www.solo.io/copy-of-system-software-engineer) In this role you'll work with a wide rage of tech like: Serverless, Docker, Kubernetes, Mesos, Linux, Unikernels, AWS and Google Cloud, Azure, ectd, istio, Golang and more. We don't expect someone coming into the role to have experience with everything, but would like someone that is excited to learn! checkout our past projects: - unik (https://github.com/cf-unik/unik) - squash (https://github.com/solo-io/squash)