The vanilla python container created with devpod and local vscode use to work perfectly but now I get this error:
Same here in bluefin-dx-nvidia,
ENAMETOOLONG
Yeah, I know it’s annoying, my vscode doesn’t fire up on it’s own neither since then…
it looks like it’s linked but I don’t know what to do with it… 
I’m thinking reinstalling bluefin
you remember what you did to end up with this error? I can’t it’s been so long now 
haha sorry for the delay.
I just used devpod to create a new devcontainer froma dockerfile and devcontainer file. I had to default to build the devcontainer using vscode tooling.
I haven’t really played with the problem since.
1 Like
Same issue here, fresh install of bluefin, add my user to docker group, open 1 devpod, and it doesn’t work.
Edit:
seems to be a nodejs problem with a devpod command being ran at startup, not really a bluefin issue
1 Like
If its a DevPod issue and you still need help, the folks at loft labs are super friendly and helpful http://slack.loft.sh/
I am hitting same issue. Local VSCode will not work with Devpod when creating workspace using any quickstart example. If I manually create a new folder with a shorter path then I am able to have Devpod open VSCode and it does not throw the ENAMETOOLONG error.
Using devpod and bluefin default paths and settings the Devpod cli logs shows info Use /var/home/user/.devpod/agent/contexts/default/workspaces/vscode-node as workspace dir.
UPDATE: I found a fix or workaround here: Cannot connect to desktop VSCode, ENAMETOOLONG · Issue #1045 · loft-sh/devpod · GitHub
Running Bluefin dx 41.20240209.1
Devpod is version v0.6.8 and cannot be updated.
VSCode is version 1.97.0
Also I noticed in the Devpod general tab the “Add CLI to Path” shows a red exclamation point identifying “Not Installed”. Quick search in the terminal devpod returns bash: devpod: command not found but the command devpod-cli functions and is located at /usr/bin/devpod-cli.
@j0rge any possibility of updating devpod versions?
Thanks
In VSCode settings. Specify the path to the ssh binary (/usr/bin/ssh) instead of VSCode trying to figure it out itself.
VSCode will bug out at times due to the PATH being longer than expected.
2 Likes
Yes, that appears to resolve the issue. I posted the github link to detailed instructions on how to change the setting:
Btw, is anyone also getting a yellow box popup when Devpod opens that displays: “Custom protocol handling needs to be configured. Either update-desktop-database or xdg-mime are missing. Please make sure they are available on your system”
Any fix for this?