f9ead06408
Updates happens multiple times, normally 2 to 3, even if we consider a state without includes. On states with multiple includes, it could easily get approximately 10 updates being ran. This behavior leads to unnecessary network bandwidth being spent and more time to run the installation state. When the connection is slow and not using the cacher, such as torified connections on Whonix, the installation can occurs much faster. Adding external repositories has to be done prior to update to ensure it is also fetched. Fixes: https://github.com/ben-grande/qusal/issues/29 |
||
---|---|---|
.. | ||
files/client | ||
clone.sls | ||
clone.top | ||
configure.sls | ||
configure.top | ||
create.sls | ||
create.top | ||
init.top | ||
install.sls | ||
install.top | ||
README.md |
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