-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
Visual Studio Code Remote: errors on connect #722
Comments
I was able to resolve this error and I can connect successfully via VSCode SSH. It appears the issue is that the Alpine Linux distro uses a more limited version of ps that does not accept the -p flag. by adding 'procps' to the 'apks' section of the addon's config file I was able to add the full featured ps command and this in turn resolved the error. I can successfully connect to my HA instance and edit code remotely. Hope this helps you @serl Here is a helpful discussion of this on nixCraft: https://www.nixcraft.com/t/how-to-install-real-ps-command-on-alpine-linux/4351 |
That is fantastic, it worked like a charm, thanks a lot! I opened a pull request to add this to the readme, just in case others fall in the same trap |
@serl do you know when an update for this addon will be cut? |
@kinghat He doesn't. It will be cut when I have spare time and when it has been tested on multiple setups on different architectures. ../Frenck |
Problem/Motivation
I used to connect Visual Studio Code to this add-on, but it stopped working recently. I tried to remove the
.vscode-server
in the remote machine, it didn't help.My guess is that's an update on Visual Studio side, so I guess I'll open a ticket there.
Am I alone in this?
Expected behavior
Use the Remote-SSH extension to connect to my Home Assistant and edit config.
Actual behavior
Gives an error, here's the log:
It seems like VSCode is calling
ps
with a little too many parameters.I found an old ticket on their side, which contains this line:
Steps to reproduce
🙏 thanks for your attention
The text was updated successfully, but these errors were encountered: