VS Code Torizon IDE Extension depends on Microsoft Docker extension
But, based on this announcement the Docker extension will be migrated to the new Container Tools extension
I think that Toradex development team is already aware of this, but I would like pointing here this future breaking change.
I think that soon or later, an update of the Torizon IDE Extension would be necessary.
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello!
The Torizon IDE extension integrates with the Docker Visual Studio Code extension to manage containers and connect with remote Torizon devices. This integration is crucial for handling Docker images, containers, and volumes during development. You can find more details in the official documentation.
Since this integration is fundamental to the Torizon IDE extension’s functionality, any updates to the Docker extension could potentially affect its operation. Therefore, it’s a good idea to keep an eye on the official Toradex documentation and community forums for any updates regarding compatibility with future changes in VS Code container tooling.
As of now, the current version of the Torizon IDE extension works seamlessly with the Docker extension as described in the documentation. It offers templates and automates tasks in Visual Studio Code necessary for cross-compilation, building Docker images, and deploying to Torizon remote devices.
If you have any more questions or need further assistance, feel free to ask.
Best regards,
Toradex AI Assistant
Greetings @vix,
Thank you for raising awareness about this. I’ll pass it on to our team just in case.
Best Regards,
Jeremias
Just to inform you, our team has taken this into account. Compatibility with the container tools extension should be available in the pre-release versions of the IDE extension at the time of writing.
Best Regards,
Jeremias
I’ve just updated the IDE extension to v3.0.109 and I see in the changelog
[NEXT]
* Add network device filter;
* Use the new Microsoft Container Extension;
But in the Dependencies I see that it depends on Docker (and not Microsoft Container)
Hey @vix
Could you send a screenshot and logs?
On our side, it seems correct, at least if you install the pre-release version.
[05-06 10:51:40.556] Activating Torizon IDE ...
[05-06 10:51:40.556] Torizon IDE version :: 3.0.109
[05-06 10:51:41.085] Latest Torizon IDE published :: 3.0.109
[05-06 10:51:41.086] Resolving host IP address ...
[05-06 10:51:43.709] Host IP address OK
[05-06 10:51:43.760] Docker installed OK
[05-06 10:51:44.072] Docker running OK
[05-06 10:51:44.252] Docker compose OK
[05-06 10:51:44.259] PowerShell OK
[05-06 10:51:44.294] git OK
[05-06 10:51:44.325] dig OK
[05-06 10:51:45.215] avahi-resolve OK
[05-06 10:51:45.250] nmap OK
[05-06 10:51:45.259] iputils-ping OK
[05-06 10:51:45.270] file OK
[05-06 10:51:45.278] sshpass OK
[05-06 10:51:45.361] iproute2 OK
[05-06 10:51:45.367] rsync OK
[05-06 10:51:45.374] python3 OK
[05-06 10:51:45.381] pipx OK
[05-06 10:51:45.382] Automatic fetch of templates is disabled
[05-06 10:51:46.946] xonsh installation OK
[05-06 10:51:46.947] Checking connected devices ...
[05-06 10:51:46.947] The torizon.autoScan setting is disabled.
[05-06 10:51:46.948] Debian bookworm packages list load OK
[05-06 10:51:46.948] Torizon IDE extension activated
[05-06 10:51:46.973] Checking host ip sanity ...
What I posted refers to the IDE extenson in Windows (that is supposed to setup a working WSL).
I cannot install a pre-release in Windows.
I suppose that your screenshot and logs comes from WSL.
I’ll do test in WSL in the next few days.
ok, got it.
Yeah, at end this dependency for Windows side does not make sense. We will remove it.
Thanks,