I had torizon working about a year ago and just getting back into the code side of things.
I decided to update to the new torizon IDE Extension on a windows 10 machine.
uninstalled the old extension and went through the new installation process. on that machine after verifying the extension when I click connect to wsl2 VS code will just hang until I close it. docker is running and I can run the a hello world.
So I decided to try on a windows 11 machine with out VS code.
on it the extension will verify but when I connect to wsl2 I do not have the Torizon extension available. after search here and trying a few items I am still stuck. docker does run a hello world
no matter which machine I try I can not get to the point were I was and connect to a device before attempting this update. Now I am a Visual studio guy and have not done much with VS code or WSL. So this is still fairly foreign to me.
so any help is appreciated but at the moment I can not use Vs code and torizon.
my wsl version is:
WSL version: 2.4.10.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5716
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.3194
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
I’m sorry to hear about the difficulties you’re experiencing with the Torizon IDE Extension on your Windows machines. Let’s go through some steps to help resolve these issues:
Verify WSL2 and Docker Setup:
Ensure WSL2 is properly installed and configured. You can check this by running wsl --list --verbose in a command prompt to confirm your distributions are running under WSL2.
Make sure Docker Desktop is set up to use the WSL2 backend, as this is crucial for integration.
Check VS Code Connection to WSL2:
Open a WSL2 terminal and type code . to launch VS Code connected to your WSL2 environment. This ensures VS Code operates within the WSL2 context.
Verify that the bottom left corner of VS Code indicates it is connected to WSL2.
Troubleshoot VS Code Hanging:
If VS Code hangs, open the Developer Tools by selecting Developer: Toggle Developer Tools from the command palette. Check the Console tab for any error messages that might indicate the cause.
Ensure Torizon Extension Visibility:
After connecting to WSL2, ensure the Torizon extension is installed in the WSL2 environment. Check the Extensions view in VS Code while connected to WSL2.
General Troubleshooting:
Restart your computer and try the setup process again to ensure all services are running correctly.
Ensure your Windows and WSL2 are up to date with the latest updates and patches.
By following these steps, you should be able to diagnose and potentially resolve the issues you’re facing. I hope this helps you get back to developing with Torizon smoothly.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
With the current information it’s hard to say what exactly could be wrong. So it just hangs? No logs or anything else to examine?
From your screenshots I see you seem to be using the installation wizard is that correct? Have you tried manual installation to see if you get a different result?
With regards to your Docker setup. Do you have Docker Desktop installed in Windows, or do you have the Docker engine installed in WSL 2? To be clear you should only have one or the other installed. Having both installed can cause strange issues.
I am still trying to figure out where to find logs for VS code. like I said I a long time VS studio user so VS code is a bit different.
Yes I used the installation wizard on a windows 11 machine. I have gone through the manual installation and made it farther at least. I can see my device and start a project from a torizon example. but now when I try to run a debugging session. I end up with the attached error. Before I opened sample project my docker would run a hello world. now I am unable to due to an incorrect username or password error. which I think is tied to the screen I am posting here.
It just seems like the information I get from the websites and links are out of sink and I am missing a step. I just know that a year ago I followed the instructions and it just worked. this time 2 pc’s both fail.
Okay this looks better. Based on the screenshot you shared, it seems like a Docker issue now. The extension is trying to start a registry container, but then it seems like the container disappears after it starts, somehow. Then it tries to start it but fails to.
How do you have Docker installed exactly? Do you have Docker Desktop in Windows, or do you have Docker engine in the WSL2 instance?
Either one can work, though typically the Docker engine in WSL2 is less problematic from what I’ve seen from others. It’s important though you only have 1 of these installed otherwise there can be strange issues.
I had docker desktop already installed. so I think that is what the torizon ide used… I am not even sure how to tell if I have in installed in WSL2.
I am going to remove everything and start over again on one machine.
I am not even sure how to tell if I have in installed in WSL2.
Do you recall running any commands in WSL 2 to install the Docker engine? If not, then you probably didn’t install it there and only have Docker Desktop.
