Talos linux `chroot: can't execute '/usr/bin/env': No such file or directory`

[felipesere]

I'm trying to connect my Talos Linux cluster to my DS923+ using this synology-csi driver. I've added the iscsi and btrfs extension to Talos.

But when creating a PVC, the driver fails with

synology-csi-node-vtbhm csi-plugin 2024-09-12T13:48:11Z [ERROR] [driver/utils.go:108] GRPC error: rpc error: code = Internal desc = rpc error: code = Internal desc = Failed to login with target iqn [iqn.2000-01.com.synology:HomeVault.pvc-568cd6e6-13f0-49ca-8bf7-d8a142c85242], err: chroot: can't execute '/usr/bin/env': No such file or directory

I'm particularly surprised by the whole chroot setup. Is there anything else I need to do? Is there a particular reason the driver chroots into the node?

[myst3k]

I have this same issue, I think this may be a fix for it: https://github.com/SynologyOpenSource/synology-csi/pull/85

[MartinLoeper]

I added a comment on the linked PR for what I had to change to make it work.

[ringods]

I would like to see this project support it out of the box, but in the meantime, have a look at this fork:

https://github.com/zebernst/synology-csi-talos

[chihyuwu]

Fixed in PR #85. After merging the PR and testing, PVC creation now works as expected.

Please test with the latest synology-csi:latest image (or with future versions starting from v1.2.1 and above). Update your node.yaml and add the --iscsiadm-path argument to specify the absolute path to iscsiadm:

- --chroot-dir=/host
- --iscsiadm-path=/usr/local/sbin/iscsiadm

Thanks to all contributors. Closing this issue.

[zetsub0u]

Quick question... why do we need all of this to begin with, why can't the container just ship iscsiadm? I remember doing that when i had to make my own csi plugin at some company i worked before and it worked fine without needing something like this.

[badnetmask]

For future reference: after the fix introduced by in PR #85, I sent a PR to the Helm chart to reflect that.

[lareeth]

I'm using the helm chart provided with this repo, The PR for it is here: https://github.com/SynologyOpenSource/synology-csi/pull/110

[badnetmask]

I'm using the helm chart provided with this repo, The PR for it is here: #110

I'm honestly having a hard time understanding who holds the upstream Helm chart. Looking at the Helm's README.md in this repo it points to the chart that I patched, and I cannot see where this repo's chart is published. The main repo README.md suggests the Helm charts are supposed to be used for development only, and they are not published anywhere.

[lareeth]

I can see how its confusing, I think the chart in this repo is based off an older version of christian-schlichtherle/synology-csi-chart but this chart has been maintained and updated (Including to v1.2.1).

I can see PRs from over a year ago in christian-schlichtherle/synology-csi-chart, including the v1.2.1 upgrade (https://github.com/christian-schlichtherle/synology-csi-chart/pull/27) that haven’t been addressed or merged

As for how to install this chart, it doesnt look like a http or oci repo has been created for SynologyOpenSource/synology-csi, however I am using GitOps tooling, like ArgoCD and Flux which both allow for pointing to a git repo, folder and tag, so that is how I have been consuming this chart