From d0ed65d13a62dd7a83910bd294922b6bfb6a02be Mon Sep 17 00:00:00 2001 From: kalipso Date: Thu, 21 Nov 2024 14:55:24 +0100 Subject: [PATCH] [docs] update microvm docu --- doc/src/anleitung/microvm.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/src/anleitung/microvm.md b/doc/src/anleitung/microvm.md index f8c9005..86f13c5 100644 --- a/doc/src/anleitung/microvm.md +++ b/doc/src/anleitung/microvm.md @@ -22,6 +22,8 @@ It seems to be necessary to run this as root so that the according tap interface To be able to ping the VM or give Internet Access to the VM your host needs to be setup as described below. ### Host Setup + +#### Network Bridge To provide network access to the VMs a bridge interface needs to be created on your host. For that: - Add the infrastructure flake as input to your hosts flake @@ -37,3 +39,14 @@ networking.nat = { externalInterface = "eth0"; #change to your interface name }; ``` +#### Auto Deploy VMs +By default no MicroVMs will be initialized on the host - this should be done using the microvm commandline tool. +But since we want to always deploy certain VMs it can be configured using the ```malobeo.microvm.deployHosts``` option. +VMs configured using this option will be initialized and autostarted at boot. +Updating still needs to be done imperative, or by enabling autoupdates.nix + +The following example would init and autostart durruti and gitea: +``` nix +malobeo.microvm.deployHosts = [ "durruti" "gitea" ]; +``` +