Error Longhorn Manager

[JulesPichon84]

Hello, I have an error while I try to install longhorn on my talos cluster with Helm chart.

 time="2025-08-25T15:06:50Z" level=fatal msg="Error starting manager: failed to check environment, please make sure you have iscsiadm/open-iscsi installed on the host: failed to execute: /usr/bin/nsenter [nsenter --mount=/host/proc/3747/ns/mnt --net=/host/proc/3747/ns/net iscsiadm --version], output , stderr nsenter: failed to execute iscsiadm: No such file or directory\n: exit status 127" func=main.main.DaemonCmd.func3 file="daemon.go:105"

I only want to deploy the longhorn resources on my workers so I setup the values like below:

# Longhorn components are only deployed on workers
global:
  nodeSelector:
    node.kubernetes.io/worker: "true"

defaultSettings:
  systemManagedComponentsNodeSelector: "node.kubernetes.io/worker=true"

For my worker config, it's here that I d'ont understand. I choosed the right image on the image factory

Then I put it on my workers config like that:

machine:
    type: worker
    install:
        image: factory.talos.dev/nocloud-installer/613e1592b2da41ae5e265e8789429f22e121aab91cb4deb6bc3c0b6262961245:v1.10.6
    kubelet:
        extraArgs:
            rotate-server-certificates: true
        image: ghcr.io/siderolabs/kubelet:${cluster_version}
        defaultRuntimeSeccompProfileEnabled: true # Enable container runtime default Seccomp profile.
        disableManifestsDirectory: true # The `disableManifestsDirectory` field configures the kubelet to get static pod manifests from the /etc/kubernetes/manifests directory.
        extraMounts:
            - destination: /var/lib/longhorn
              type: bind
              source: /var/lib/longhorn
              options:
                - bind
                - rshared
                - rw
    nodeLabels:
        topology.kubernetes.io/region: ${target_node}
        topology.kubernetes.io/zone: ${cluster_zone}
        node.kubernetes.io/worker: true

Finally, when I lookup for the binaries that are setup in my workers, I have that:

talosctl ls -r /usr/local -n 192.168.1.222 --talosconfig .\output\talosconfig   

NODE            NAME
192.168.1.222   .
192.168.1.222   lib
192.168.1.222   lib/kubelet
192.168.1.222   lib/kubelet/credentialproviders
192.168.1.222   share
192.168.1.222   share/ca-certificates
192.168.1.222   share/schematic
192.168.1.222   share/schematic/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba

Thank you for the response !

[smira]

It looks like you don't have iscsi-tools installed.

You can check with talosctl get extensions.

As you don't specify your environment it's hard to guess what is wrong, but that is the problem.

[rothgar]

That schematic version is different than what you posted in the first question. Try upgrading to the correct version with extensions via

talosctl upgrade --image factory.talos.dev/nocloud-installer/613e1592b2da41ae5e265e8789429f22e121aab91cb4deb6bc3c0b6262961245:v1.10.6

[smira]

I used the nocloud installer for proxmox hypervisor.

You probably you used nocloud disk image, so there is no install happening there. You need to use a disk image with a proper schematic, and you're good to go.

[JulesPichon84]

Sorry, I'm not sure I understand correctly. To create my proxmox vm template, I used these commands:

wget https://factory.talos.dev/image/376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba/vX.Y.Z/nocloud-amd64.raw.xz

# Decompress the image
unxz nocloud-amd64.raw.xz

# Create the template and give it a name and an ID (≠0)
qm create $ID --name $NAME

# Attach the image to the template
qm set $ID --scsi0 local-lvm:0,import-from=/path/to/nocloud-amd64.raw

# Apply the template
qm template $ID

So if I understand correctly, it is necessary that the image which is downloaded on my proxmox server must have the binaries:

• siderolabs/iscsi-tools
• siderolabs/util-linux-tools

And so after, I recreate a template with the custom image and I put the same image for my machine config. Am I right ?

[smira]

See yourself - you are using wrong schematic in the disk image - 376567988ad370138ad8b2698212367b8edcb69b5fd68c80be1f2ec7d603b4ba vs. 613e1592b2da41ae5e265e8789429f22e121aab91cb4deb6bc3c0b6262961245 you need.

Just follow https://factory.talos.dev/?arch=amd64&cmdline-set=true&extensions=-&extensions=siderolabs%2Fiscsi-tools&extensions=siderolabs%2Futil-linux-tools&platform=nocloud&target=cloud&version=1.10.6

It has a note that "initial install" is not used for disk images.

[JulesPichon84]

Ok, thank you for the help !