https://github.com/robur-coop/unikernels

MirageOS unikernels
https://github.com/robur-coop/unikernels

dns letsencrypt mirageos unikernel

Last synced: about 1 month ago
JSON representation

MirageOS unikernels

• Host: GitHub
• URL: https://github.com/robur-coop/unikernels
• Owner: robur-coop
• Created: 2018-11-14T18:40:51.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2021-10-09T14:45:16.000Z (almost 3 years ago)
• Last Synced: 2024-07-18T05:36:59.997Z (2 months ago)
• Topics: dns, letsencrypt, mirageos, unikernel
• Language: OCaml
• Size: 156 KB
• Stars: 50
• Watchers: 12
• Forks: 6
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Unikernels

[![Build Status](https://travis-ci.org/roburio/unikernels.svg?branch=master)](https://travis-ci.org/roburio/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](https://mirage.io/wiki/install)

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](https://mirage.io/wiki/hello-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](https://github.com/solo5/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`](primary/) subdirectory contains an unikernel with the hardcoded

zone (in its [unikernel.ml](primary/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`](primary-with-zone/) contains no hardcoded

configuration, but serves [`data/zone`](primary-with-zone/data/zone) instead.

## Let's encrypt certification unikernel

The [`certificate`](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`](resolver/) subdirectory contains an iterative resolver.

The [`stub-resolver`](stub-resolver/) subdirectory contains a stub resolver,

which forwards all requests to `141.1.1.1`.