chore: move omada storage to pve bind mount
This commit is contained in:
14
202-omada.tf
14
202-omada.tf
@@ -33,6 +33,20 @@ resource "proxmox_lxc" "omada" {
|
|||||||
mount = "nfs;cifs"
|
mount = "nfs;cifs"
|
||||||
}
|
}
|
||||||
|
|
||||||
|
// Bind Mount Point
|
||||||
|
mountpoint {
|
||||||
|
key = "1"
|
||||||
|
slot = 1
|
||||||
|
storage = "/mnt/lxc/omada"
|
||||||
|
// Without 'volume' defined, Proxmox will try to create a volume with
|
||||||
|
// the value of 'storage' + : + 'size' (without the trailing G) - e.g.
|
||||||
|
// "/srv/host/bind-mount-point:256".
|
||||||
|
// This behaviour looks to be caused by a bug in the provider.
|
||||||
|
volume = "/mnt/lxc/omada"
|
||||||
|
mp = "/data"
|
||||||
|
size = "1G"
|
||||||
|
}
|
||||||
|
|
||||||
network {
|
network {
|
||||||
name = "eth0"
|
name = "eth0"
|
||||||
bridge = "vmbr0"
|
bridge = "vmbr0"
|
||||||
|
Reference in New Issue
Block a user