Thank you for providing your system information! You’re running Torizon OS 7.4.0-build.28 on a Colibri iMX7D 1GB (eMMC) on Colibri Evaluation Board V3.
Understanding the Registry Error Pattern
The intermittent nature of your issue (working for 4-5 runs, then failing) is a common pattern with the Torizon IDE Extension’s local Docker registry functionality. This typically indicates resource exhaustion or network interface confusion rather than a fundamental configuration problem.
Troubleshooting Steps
1. Check Network Configuration
The error suggests the extension is having trouble reaching the local Docker registry on port 5002 (1). Since you mentioned this happens after several successful runs, this points to a potential IP address detection issue.
You can configure the torizon.overwriteHostIp setting in VS Code to specify the correct IP address of your development machine (1). To do this:
- Open VS Code Command Palette (F1)
- Select “Preferences: Open Settings (JSON)”
- Add the following line with your development machine’s IP:
"torizon.overwriteHostIp": "YOUR_DEV_MACHINE_IP"
(1)
2. Verify Required Ports
The Torizon IDE Extension requires these ports to be accessible (1):
- 22 (SSH Connection) -
You confirmed this works
- 2375 (Docker API)
- 5002 (Local Docker Registry) - This is where your error occurs
- 2222 (Container SSH Connection)
3. Check for SSH Connection Issues
The error shows SSH exit status 7, which typically indicates connection problems. You can test the SSH connection manually (1):
ping -W 1 -c 1 <your-device-ip>
(1)
If you get “Operation not permitted”, run:
sudo setcap cap_net_raw+ep /bin/ping
(1)
4. Registry Connectivity Test
The extension is trying to connect to http://localhost:5002/v2/_catalog on your device. This suggests the local registry on your development machine should be accessible from the device at that address.
Why It Works Initially Then Fails
This pattern typically occurs because:
- Resource buildup: After multiple deployments, temporary containers or network connections may accumulate
- Registry state: The local Docker registry may become unresponsive after handling multiple requests
- Network interface confusion: Your development machine may have multiple network interfaces, and the extension might lose track of the correct one
Recommended Solution
Try restarting VS Code and your development machine’s Docker service between deployment sessions. This will reset the local registry and clear any accumulated network state.
The torizon.overwriteHostIp setting mentioned above is often the most effective permanent solution for this type of intermittent connectivity issue (1).
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
