I’m getting the following when trying to download and debug an application from VSCode. Lot’s of things seem to be working OK to get to this point, however I don’t know what the password is supposed to be here. It looks like it should be the torizon user password on the device, but that doesn’t work.
Warning: Permanently added ‘[192.168.1.121]:2222’ (ECDSA) to the list of known hosts.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0777 for ‘/mnt/c/Software/XXXX/YYYYYY/appconfig/.conf/id_rsa’ are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key “/mnt/c/Software/XXXX/YYYYYY/appconfig/.conf/id_rsa”: bad permissions torizon@192.168.1.121’s password:
Permission denied, please try again. torizon@192.168.1.121’s password:
Permission denied, please try again.
The password is for the TorizonCore user that you used to connect the SoM to the extension, usually torizon. So you’re probably entering the correct password.
From the message you got the user permissions for your SSH key are considered too open for the SSH client, so it refuses to connect.
I’m assuming you’re using Windows on the host machine, is this right? If so, try following the suggestions detailed on this page to see if you can limit the SSH key permissions to your current user on the host machine:
So it turns out that this is related to having the project on a Windows drive but running the WSL version of the tools.
I was unable to install the new extension in VS Code - there was an error regarding support for 64-bit. Is that something that will be fixed?
I just tried a test project created in the WSL file system and that works fine.
OK, so apparently you were using V1 of the IDE extension on WSL2. Keep in mind that we designed V1 of the extension to be used directly on Windows, not inside WSL2, as said here: Visual Studio Code Extension for Torizon | Toradex Developer Center . Using it inside WSL2 could cause unexpected behavior like the SSH key permission issue you experienced.
I was unable to install the new extension in VS Code - there was an error regarding support for 64-bit. Is that something that will be fixed?
I just tried a test project created in the WSL file system and that works fine.
This message is expected, as V2 of the extension was made to be used only inside WSL2 on Windows systems. We don’t allow it to be installed outside of it.
Hello @msmith ,
Were you able to try the alternative that @lucas_a.tx proposed?
If you did so and it was successful, please mark his answer as solution.
I’m still working through porting our solution to the V2 tools, but that seems to be OK now.
I was a little confused as the new extension shows up in the list in VSCode for Windows but the answer from Lucas clarifies things.
How are things looking for the multi-container project support? When do you expect that to be ready for production use?
We have a .NET app in a container running our core application and Qt in another container.
I have another open issue with some more details on our Qt issues:
You can start playing with it now with the caveat that it may change in breaking ways before it is finally released. You will need to enable experimental features in the VSCode Torizon extension settings. See here for more details.
