-
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.md
53 lines (39 loc) · 1.27 KB
/
README.md
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
# shoes-lxd
shoes-provider for [LXD](https://linuxcontainers.org/lxd/)
## Setup
please set Environment values
### Required values
`shoes-lxd` needs information of worker.
use `LXD_HOSTS` and ignore `LXD_HOST` if set both.
#### for single worker
- `LXD_HOST`
- FQDN or IP address of running LXD daemon
- `LXD_CLIENT_CERT`
- File path of client cert
- `LXD_CLIENT_KEY`
- File path of client cert key
#### for multi worker
- `LXD_HOSTS`
```json
[
{
"host": "https://192.0.2.100:8443",
"client_cert": "./node1/client.crt",
"client_key": "./node1/client.key"
},
...
]
```
### Optional values
- `LXD_IMAGE_ALIAS`
- set runner image alias
- default: `ubuntu:bionic`
- e.g.) for remote image server: `https://192.0.2.110:8443/ubuntu-custom`
- `LXD_RESOURCE_TYPE_MAPPING`
- mapping `resource_type` and CPU / Memory.
- need JSON format. keys is `resource_type_name`, `cpu`, `memory`.
- e.g.) `[{"resource_type_name": "nano", "cpu": 1, "memory": "1GB"}, {"resource_type_name": "micro", "cpu": 2, "memory": "2GB"}]`
- become no limit if not set resource_type.
## Note
LXD Server can't use `zfs` in storageclass if use `--privileged`. ref: https://discuss.linuxcontainers.org/t/docker-with-overlay-driver-in-lxd-cluster-not-working/9243
We recommend using `btrfs`.