RudderVirt

#Recipes

Full worked examples for the situations you are most likely to hit.

Each recipe is a complete YAML manifest. To use one, open a build in the editor, switch to the YAML tab, paste the recipe in, and adjust the URLs, credentials, and provisioner steps to match what you are building. The individual fields are explained in the linked concept pages, which also show where each one lives in the visual editor.

  • Linux from a Cloud Image — The easy path. Cloud images come pre-installed and pre-configured for cloud-init. You just boot, provision, capture.
  • Linux from an ISO — When there is no cloud image (or you need a specific install layout), boot from an ISO and drive the installer with a preseed/kickstart file served via the HTTP directory.
  • Hello World — The shortest useful build: a single-VM module that boots a Debian 12 cloud image.
  • Windows from an ISO — Windows builds are the hardest case. Paste the YAML blocks below into the editor's YAML tab; the concept pages explain each field and where it appears in the visual editor when one of the modes hides it.
  • Multi-VM Builds — A multi-VM module. The VMs boot in parallel, share networking, and each becomes a template VM in the resulting module. Clones spin up running copies of all of them as a group.
  • Layered Builds — A build can take its source from another build's output. This is how you compose a stack of modules, each layering on top of a previous one. In the visual editor, this is the Existing Image source option on a VM; in YAML, it is source.buildRef. See Sources for the field walkthrough.
  • Sample Autounattend — Find and replace any references to YOUR with values that suit your build. IE YOURCOMPUTERNAME, YOURUSERNAME, YOURUSER, YOURPASSWORD, etc.