Error from daemon: No such container: torizon-ide-port-tunnel *

Technical Support
, , , ,
1

I had to reenable the binfmt.service under WSL (did you guys not use that before?). However, now I have a different problem.
After is pushes the image to the local registry it tries to execute:
spin-up-down-registry.xsh, which retries a bunch of times because the torizon-ide-port-tunnel is not available.

Steve

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I can help troubleshoot this WSL-specific issue with the local registry and port tunneling. This appears to be related to port forwarding configuration in the WSL environment.

Port Forwarding Requirements

The Torizon IDE Extension requires specific ports to be accessible between your machine and the development board (1):

  • 22 (Dev Board SSH Connection)
  • 2375 (Docker API)
  • 5002 (Local Docker Registry)
  • 2222 (Container SSH Connection)

WSL Port Sharing Configuration

The extension includes a specific script to handle WSL port sharing issues. The share-wsl-ports.xsh script is designed to open the firewall from the Windows side and make WSL ports accessible from the target device (2). This script runs automatically when the extension is activated, but only executes the actual code if in a WSL 2 environment (2).

Local Registry Configuration

By default, the Torizon IDE Extension stores container images in local registries without additional setup (3). The local registry typically runs on port 5000 (3):

$ docker run -d -p 5000:5000 --name registry registry:2

(3)

Troubleshooting Steps

  1. Check Host IP Configuration: If you’re experiencing registry connection issues, the extension may not be getting the correct IP address of the host. This can happen when the host is using VPN or other network configurations that change the IP address or have multiple interfaces (1).

  2. Set Host IP Override: You can set the torizon.overwriteHostIp setting in VS Code global settings to the correct IP address from the main interface that the host is using (1).

  3. Verify Port Accessibility: Ensure all required ports (especially 5002 for the local registry) are accessible in your WSL environment.

  4. Check WSL Firewall: The share-wsl-ports.xsh script should handle this automatically, but you may need to manually verify that Windows firewall allows these ports through.

Could you let me know which specific version of Torizon OS and which hardware platform you’re using? This will help me provide more targeted troubleshooting steps. You can use the tdx-info command to get this information: Getting Device Information with Tdx-Info | Toradex Developer Center

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.