Skip to content

Commit

Permalink
README: add lxd-vm backend, mention memory limit support for both lxd…
Browse files Browse the repository at this point in the history
… and lxd-vm backends

Signed-off-by: Maciej Borzecki <maciej.borzecki@canonical.com>
  • Loading branch information
bboozzoo committed Mar 28, 2024
1 parent 5d6afcf commit 77fbb21
Showing 1 changed file with 30 additions and 0 deletions.
30 changes: 30 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down Expand Up @@ -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:
```

<a name="lxd-vm"/>

## 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.

<a name="qemu"/>

Expand Down

0 comments on commit 77fbb21

Please sign in to comment.