<@U096F6RRP6D> Hi team, I’ve cloned all the reposi...
# harvester
m
@sparse-vr-27407 Hi team, I’ve cloned all the repositories for Harvester and its components. I followed the build process to create a custom ISO image: • Built the UI from the
harvester-ui-extension
repo using the
build-embedded
script and hosted the resulting UI build. • Used that hosted UI URL in the
Dockerfile
inside the main Harvester repo. • Finally ran
sudo make build-iso
, and the ISO image was successfully created in the
dist
directory. I deployed this locally built ISO on a 2-node server, but I’m encountering an issue with VM creation functionality (fails during volume attachment). However, when I deploy the official ISO from Harvester releases, it works fine on the same 2-node cluster — VM creation proceeds without issue. Could help me understand why this discrepancy exists? Is there any known caveat or required change when customizing and building ISO locally?
a
I think the key point here is:
CSINode orion0 does not contain driver <http://driver.longhorn.io|driver.longhorn.io>
Is Longhorn correctly installed on this node?
👍 1
m
yes longhorn is correctly installed and i am accessing longhorn UI as well.
as you can also check the longhorn UI for nodes
s
You have only this 2 node as Longhorn Node, right ?
m
yes , currently i have 3 node as Longhorn Node Hi, I'm having issues attaching the CD-ROM (root disk) volume to a VM. In the Longhorn UI, the volume shows as "Attaching" status. The same VM has a storage volume attached successfully, but the CD-ROM is not attaching. As a result, the guest VM is not in a running state.
ls