-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finding installed ssh failed: spawn ENOTDIR #4630
Comments
Got the same issue as well, macOS Big Sur 11.2.2. VSCode
Seems also to be affecting remote containers. |
Confirming that downgrade to 1.53.2 solved the issue for both SSH and containers. |
I'm having the same Version: 1.54.1 I thought the fix that came in microsoft/vscode#118124 might fix it but it hasn't. |
I Got the same issue. Same versions as above. Fixed it with downgrading |
I cannot reproduce this issue. However, this issue might occur when the |
ty @tamuratak, I cleaned up my PATH variable and now the error is gone
|
Can you clarify what you changed in your PATH? |
And, can someone clarify what the error is for Remote-Containers and share whatever screenshot or log might look useful? |
Can anyone check whether setting |
This doesn't make a difference for me. Still the same error. |
And to clarify, this issue is only for getting this while trying to connect with Remote-SSH, and seeing the log in the original post. Getting this while opening a Jupyter notebook: make sure you've gotten the 1.54.1 update, and if so, open a new issue or check microsoft/vscode#118124. If you think you are seeing the same SSH issue, also please include your log from the @initial-wu this line in your log: |
@initial-wu or anyone on facing this issue, can you print your |
Is this helpful?
|
i meet the same issue |
We are able to reproduce it - if your PATH variable includes a path to a file, then this will be triggered. Looking into a fix, but in the meantime, check that your PATH includes only folders, not files. |
@roblourens this is the error I get when trying to attach to a container: Obviously Docker daemon is running (connected to remote container in 1.53.2). |
Hidden my previous comment, was a fish config issue. My
Somehow pyenv got /Users/omer.a/.pyenv/libexec/pyenv in there, still trying to figure out how but was able to remove it programmatically when loading my shell. |
We just released an update to VS Code Insiders that has this fix. Please try it out and let me know how it goes. |
@roblourens sorry for the delay, I removed old and missing paths |
Works for me, thanks for the quick fix! |
🎉 and we just released this to stable as well in 1.54.2 |
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: No
The text was updated successfully, but these errors were encountered: