05:26 <ehirdoy1> Hello, How do you orchestrate MirageOS/Hvt? I statically set up tap devices and bridged to eth0, but any better way along with Containers? I happened to find Nabla **runnc** planning MirageOS support. https://github.com/nabla-containers/runnc

08:49 <dinosaure> ehirdoy1: currently, from what I know, we deploy an unikernel by hands or with the hannes's project albatross

08:50 <dinosaure> I did not use it (where I deployed by hands, configure bridge and so on)

10:41 <hannes> yes, I use albatross https://github.com/hannesm/albatross for this. there's as well libvirt (if you configure with -t virtio and -t xen, I think a libvirt configuration file is generated)

10:43 <hannes> I also found this repository https://github.com/keyfender/deployment that seems to integrate solo5-kvm with kubernetes

13:08 <ehirdoy1> Good info! Thanks! I guess probably it's better to orchestrate my MirageOS instances in the same manner as normal Contianers....

13:22 <ehirdoy1> Is keyfenfer a solo5(VM) in a minimal Container? ;)

13:39 <apache2> a "container" in this context is usually NOT a virtual machine, it is more comparable to a chroot in the sense that it's an environment that uses the host OS kernel and interacts directly with it through system calls.

13:40 <apache2> Solo5 does not implement anything to do with "containers," although it does provide a mechanism to run program sandboxed using seccomp inside Linux, the "SPT" target.

13:41 <apache2> this means that container orchestration frameworks are not useful for running mirage, but virtal machine orchestration tools are the relevant technology.

13:42 <apache2> you could for instance use Albatross or virt-manager, but not Docker.

13:43 <apache2> Kubernetes is a bit special in this regard; it can do both, see http://kubevirt.io/

13:44 <apache2> if you want to use containers you could use solo5-spt inside a container, which would let you use something like docker or kubernetes directly.

13:45 <apache2> (or you could use the mirage-unix target directly)