qusal/salt/mirage-builder
2024-07-01 09:14:53 +02:00
..
files/client fix: remove expired GitHub web-flow signing key 2024-07-01 09:14:53 +02:00
clone.sls refactor: initial commit 2023-11-13 14:33:28 +00:00
clone.top refactor: initial commit 2023-11-13 14:33:28 +00:00
configure.sls refactor: prefer systemd sockets over socat 2024-06-25 22:16:26 +02:00
configure.top refactor: initial commit 2023-11-13 14:33:28 +00:00
create.sls refactor: prefer systemd sockets over socat 2024-06-25 22:16:26 +02:00
create.top refactor: initial commit 2023-11-13 14:33:28 +00:00
init.top refactor: initial commit 2023-11-13 14:33:28 +00:00
install.sls fix: remove extraneous package repository updates 2024-03-18 17:51:36 +01:00
install.top refactor: initial commit 2023-11-13 14:33:28 +00:00
README.md doc: nested list indentation 2024-05-14 18:43:07 +02:00
version fix: generate RPM Specs for Qubes Builder V2 2024-06-21 17:00:06 +02:00

mirage-builder

Mirage Builder environment in Qubes OS.

Table of Contents

Description

Setup a builder qube for Mirage Unikernel named "mirage-builder". The tool necessary to build Mirage with docker or directly with Opam will also be installed.

Installation

Mirage Firewall commits and tags are not signed by individuals, but as they are done through the web interface, they have GitHub Web-Flow signature. This is the best verification we can get for Mirage Firewall. If you don't trust the hosting provider however, don't install this package.

  • Top:
sudo qubesctl top.enable mirage-builder
sudo qubesctl --targets=tpl-mirage-builder,mirage-builder state.apply
sudo qubesctl top.disable mirage-builder
  • State:
sudo qubesctl state.apply mirage-builder.create
sudo qubesctl --skip-dom0 --targets=tpl-mirage-builder state.apply mirage-builder.install
sudo qubesctl --skip-dom0 --targets=mirage-builder state.apply mirage-builder.configure

Usage

The qube mirage-builder is intended to build Mirage Unikernel. Consult upstream documentation on how to build qubes-mirage-firewall from source.

If you plan to build without docker, the hooks and completion scripts are already being sourced by your shell profile. Because of this, when calling opam-init, use it together with the option --no-setup:

opam init --no-setup