Problems with the Torizon IDE

[bruno.tx]

Hello @gerko,

Thanks for the clarifications.

@gerko

• Do you also test on a separate Ubuntu 22.04 installation, or only as a WSL 24.04 Ubuntu installation?
• Do you test with multiple projects open?
• Or do you sometimes open other projects while working on one project?

I tested in a system with multiple VSCode windows open, but only a single Torizon IDE project.
I don’t think that multiple projects open should impact anything, unless one of them is actually running.
My system is Debian 12, but I know our IDE team tests both with ubuntu and ubuntu under WSL.
The OS used could be relevant here.

---

@gerko

I actually tested it with a fresh C# console project and I get the ssh-check errors in root mode… regardless of whether all other containers are removed or not.

Did you try with a board that had been rebooted after the containers were stopped?
It is conceivable to me that containers configured the network interface in a way that triggers the problem, then, if the container is stopped but the system not rebooted, the configuration will persist.

---

@gerko

For example, in a current project, the run-container-release-arm64 task results in the following error message:

Executing task: sleep 1 && DOCKER_HOST=10.100.1.79:2375 docker pull localhost:5002/networktracingapi:0.0.8 

Error response from daemon: manifest for localhost:5002/networktracingapi:0.0.8 not found: manifest unknown: manifest unknown

This issue actually looks like the following problem: Unable to run projects with docker "containerd snapshotter" backend (docker >=29) · Issue #427 · torizon/vscode-torizon-templates · GitHub

The workaround described in the following thread should avoid this problem: Docker 29.x on Ubuntu causes "no matching manifest for linux/arm64/v8" and Compose v5.0.0 crash

Best Regards,
Bruno