Hi Ten64 community,
I have just received my NAS ten64, and one of the reasons for me to buy a ten64 for me was the chance to manage a k3s cluster like proxmox within openwrt.
Here are some caveats I found so far…
First, I needed to work with latest k3os-cluster-wizard from gitlab’s master branch.
Second, the muvirt-system-setup filesystem partition for working area/cache and swap seems to have a little bug, as a lsblk shows afterwards the SWAP partition size that belongs to working area/cache and the opposite (SWAP partition size attached to lvm)
Third, I found that the that muvirt’s k3os script fails at downloading new images from scratch as the path /mnt/scratch/imglibrary does not exists after applying muvirt-system-setup, so it has to be created in advance.
Fourth, when provisioning new k3os VMs, precisely the line 142
newVMConfig[“imagesum256”] = sha256sum
should be replaced by
newVMConfig[“checksum”] = sha256sum
by looking at the lua call.
Fifth, and this is where I am stuck, it fails at creating volumes for the VMs with the following:
user.notice muvirt-provision: [Could not create a volume for k3controller]
Is there anything I am missing? How can I debug this?
Last, I noticed that It can’t create volumes from SATA’s SSD due to zlib on filesystem. I installed muvirt from the appstore to the nvme as the quickstart doc suggests.
I’d like to know also if it’d be possible to add external storage to all the new VMs as shared volumes on k3os (eg. longhorn use case) and how to make it work on SATA.