I would like to have my custom /var/lib/vz. Would like guidance on content storage paths - I don't know where to store CT images.

Replicant

Member
May 31, 2021
11
4
8
42
I have multiple standalone PVE hosts that all have their own ZFS pools. Inside each pool I would like to have my custom "var-lib-vz" ZFS dataset (this filesystem will be synced using syncthing running in LXC on each host).

The main reasoning for this setup is:
  • One centralized location for iso images and CT templates
  • Back up a CT on one host and restore it on another
  • Some hosts are in regions that can't connect to the template URLs or Linux distro sites. By downloading on one host, they will be available on others.

I will be using this "var-lib-vz" dataset as a directory storage type. I don't think syncthing can handle zfs volumes (nor do I plan to do so). So really, it's not "ZFS" in any way - it's just a directory.

Here are the content types that "directory" supports. I plan to use the exact naming scheme that proxmox does as well:

images: VM disk images
path:
Code:
/var-lib-vz/images/VMID

rootdir: CT disk images
path: I can't find this information

vztmpl/iso: CT templates / VM iso images
path:
Code:
/var-lib-vz/template/[iso|cache]

backup: backups of CT/VM
path:
Code:
/var-lib-vz/dump

snippets: I don't use these

My questions are:

1. Sanity check: does this implementation make sense?
2. Is my understanding of the content types and their paths correct?
3. Where are CT disk images stored on a "directory" storage type? I have not been able to find this from searching the web, I don't deny maybe I missed it. ChatGPT says
Code:
/var/lib/vz/rootdir
 
Last edited: