I’ve just updated my version of Docker Desktop to the same as yours. I can still install and run the VSCode extension fine it seems. What made you suspect that the issue was with the version of Docker Desktop?
By attachments I mean the screenshots above.
Suspecting it is a docker issue, because I can recently remember docker being updated. It may not be the case.
If you check the first screenshot, it tells that add device command not found. Issue likely caused by extension that contributes torizon.addDevice.
Apart from this in the output console in VScode (in Pty host), I am also getting the warning as below.
[warning] Shell integration cannot be enabled for executable “c:\Users\user-folder.vscode\extensions\toradex.torizon-early-access-1.6.5\moses-windows\moses.exe” and args [“–port”,“5000”]
In output console for Torizon, I get the following:
[00-10 11:47:14.911] Initializing Torizon Extension
[00-10 11:47:14.913] Checking system setup…
[00-10 11:47:15.479] Checking Moses …
[00-10 11:47:15.479] Starting backend local instance running on port 5000
[00-10 11:47:57.534] Cannot connect to Torizon IDE backend process.
After consulting with our extensions team, they suspect possibly a corrupted file path or something similar. They recommend manually deleting the c:\Users\user-folder.vscode\extensions\toradex.torizon-early-access-1.6.5\ and c:\Users\user-folder.vscode\extensions\toradex.torizon-1.5.1 folders and reinstalling the extension may solve the problem.
I have tried deleting these folders but I am still getting the same issue. I have also re-installed VSCode and tried the steps at stackoverflow, but I am still getting the same error.
Conversely however, within WSL I started VSCode and installed the Toradex support extension, it went ahead smoothly . I know it is not supported within WSL and ApolloX is but both installed perfectly in WSL.
However back in the windows environment, I have the same issue with the Toradex plugin. It appears that there is a WSL setting in the Toradex support extension that might be causing this issue?
Because if this issue were to be with vscode, then should’nt I have had the same issue within WSL?
On a seperate thread, I found the following link to WSL ports
This is an issue when trying to use WSL behind a VPN and the port numbers used include port number 5000.
Is there a way moses.exe can use a different port number apart from 5000?
The setting you’re looking for is “Torizon: Backendport”. Then once you set an alternate port you can restart and it should be using this port now.
Just to make sure I understand, are you saying that the reason the extension wasn’t working in Windows was because port 5000 was already in use by something else on your system? Or is this related to WSL?