06:27 <ehirdoy1> apache2: I think I understood what you mentioned. My point was that, container orchestration is too popular to ignore now. Hooking in OCI/CRI(container standard) may get things easier for Unikernel so that Nabla uses runnc.

06:37 <apache2> I don't think I am as optimistic about containers as you, but it is a fair use-case. :) And yeah, since mirage can compile for `unix` targets you can use mirage with pretty much any container system you can think of (docker,kubernetes,w/ever). I would recommend the solo5-spt target over nabla if you can get away with that, I'm not sure how maintained nabla is?

06:41 <ehirdoy1> For SPT, IIUC, it's a kind of hybrid? or "Unikernel as a process, restricted by seccomp"? Its point is high performance with some protection because it doesn't switch KVM context? and spt ~= nabla?

10:38 <mato1> ehirdoy1: apache2: It is possible with some tricks to run either Solo5 hvt (if you're on bare metal) or spt inside OCI/docker containers. But the infrastructure to integrate that is no longer maintained from our side. See e.g. my old project https://github.com/mato/docker-unikernel-runner.

10:39 <mato1> ehirdoy1: If you're interested in that I'd recommend collaborating with the nabla folks.

10:54 <ehirdoy1> mato1: Thanks for the info!! I am assuming that your previous effort is a kind of interitted by Nabla for spt( in addition to hvt???) Or did they drop to support hvt?

10:56 <mato> ehirdoy1: No, my previous effort is entirely unrelated, back from when I worked for Unikernel Systems/Docker.

10:57 <mato> ehirdoy1: The nabla folks are mainly interested in spt as they want to run on clouds that don't give you access to hardware virtualization. I've not looked into their OCI integration in any detail, but I guess it should be possible to use hvt with it.