From 77fbb2158f2840e845ea2568e1597087167e06c0 Mon Sep 17 00:00:00 2001 From: Maciej Borzecki Date: Thu, 28 Mar 2024 14:45:49 +0100 Subject: [PATCH] README: add lxd-vm backend, mention memory limit support for both lxd and lxd-vm backends Signed-off-by: Maciej Borzecki --- README.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/README.md b/README.md index fd5f21f8..5cd90748 100644 --- a/README.md +++ b/README.md @@ -23,6 +23,7 @@ Spread [Disabling unless manually selected](#manual) [Fetching artifacts](#artifacts) [LXD backend](#lxd) +[LXD VM backend](#lxd-vm) [QEMU backend](#qemu) [Google backend](#google) [Linode backend](#linode) @@ -805,6 +806,35 @@ backends: That's it. Have fun with your self-contained multi-system task runner. +The LXD backend supports setting memory limit for the containers like so: + +``` +backends: + lxd: + memory: 1024M + systems: + - ubuntu-16.04: +``` + + + +## LXD VM backend + +The LXD VM backend works very much the same as the LXD backend, but instead of +containers it spins up LXD VMs. + +Assuming LXD was successfully installed and configured, setting up the backend +in your project file is as trivial as: + +``` +backends: + lxd-vm: + systems: + - ubuntu-22.04 +``` + +The image naming and resource limits rules are identical to the LXD backend. By +default, each VM is created with a single CPU and 1GB memory limit.