Unikernels

A MirageOS unikernel repository

All source code in this repository was developed from scratch by the specific authors. This code is put in the public domain.

If you want to use them in a corporate environment, and avoid any legal issues, you can buy a license, please contact https://robur.io

Installation

Dependencies

Follow the MirageOS installation instructions unless you already have OCaml (at least 4.08.0), opam (at least 2.0.0), and the mirage command line utility (at least 3.7.7 from May 2020) installed.

In any of the subdirectories, run mirage configure (see mirage help configure for options), followed by make depend and make (read more information Hello MirageOS world).

Depending on the target, the name and type of the resulting binary varies. In the default target, unix, its name is ./main.native, and which may require superuser privileges to listen on privileged ports (use doas (or sudo) ./main.native -l \*:debug).

If you want to compile for Linux KVM, FreeBSD BHyve, OpenBSD VMM (by using solo5), run mirage configure -t hvt (or -t virtio for Google Compute Engine).

All unikernels use the default stack implementation, and thus will listen on 10.0.0.2/24, their gateway being 10.0.0.1.

Primary authoritative nameservers

The primary subdirectory contains an unikernel with the hardcoded zone (in its unikernel.ml) named mirage and some resource records. It also configures several TSIG keys, one for the secondary, one for update operations and another one for transfer operations.

The primary-with-zone contains no hardcoded configuration, but serves data/zone instead.

Let's encrypt certification unikernel

The certificate subdirectory contains an unikernel which receives a key seed, and looks in DNS for a let's encrypt certificate. If none is found, a certificate signing request (TLSA record, type private (255)) is put into DNS, and DNS is polled until a certificate occurs.

Caching resolvers

The resolver subdirectory contains an iterative resolver.