I just upgraded to Electric Eel and I no longer have the ability to SSH in with vscode. I can ssh in just fine via a terminal. SSH is turned on and AllowTCPForwarding is set to on as well.
However, when I try and use vscode, the server side application fails to run. I get the following error:
Error: Couldn't install vscode server on remote server, install script returned non-zero exit status
Has anyone ran into this? I have tried vscodium (as well as zed) and they fail on the server side every time.
See 24.10.1 release notes:
The boot pool is now properly enforcing the default setuid and noexec options (NAS-127825). This restores the default boot pool behavior to be restricted from general use. Users that are currently attempting to exec scripts from a /home or other boot pool location should move these to a data pool location.
There was an upstream ZFS bug whereby noexec was not being properly enforced on boot pool datasets.
Appreciate the responses! Sorry for my ignorance, but if I understand correctly, then I would need to use a default location other than /home/username as my SSH home directory so it will execute the server script.
If that is the case, would you have any advice on a recommended ādata pool locationā? Iāve only ever seen ā/home/usernameā as the standard location
Somewhere on your literal pools, like so:
/mnt/tank/vscode
Replacing tank with one of your poolnames and adjusting vscode for whatever dataset you want to keep this in (and have created).
Ah, got it working! Thank you all!
1 Like
What did you need to change to get it working?
