I am deploying projects using Visual Studio Code on Torizon IDE with a WSL2 environment. My setup includes a Verdin development board with an i.MX8MP chip. My PC has the IP address 192.168.1.205, and the Verdin board is assigned 192.168.1.29.
Everything was working fine until recently, when I started encountering the following error during deployment:
1 error occurred:
* Error response from daemon: Get "http://192.168.1.205:5002/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
* The terminal process "/bin/bash '-c', 'DOCKER_HOST=192.168.1.29:2375 LOCAL_REGISTRY=192.168.1.205 TAG=arm64 GPU=-imx8 DEBUG_SSH_PORT=2222 DEBUG_PORT1= DEBUG_PORT2= DEBUG_PORT3= docker compose --ansi never pull adc-debug'" terminated with exit code: 18.
It seems like there’s a timeout issue while accessing the Docker daemon or the registry. Could you help me understand:
1. What might be causing this error?
2. How can I troubleshoot and resolve it to ensure smooth deployment?
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
I’m sorry to hear about the timeout issues you’re experiencing during Docker deployment with Torizon IDE on your WSL2 environment. Let’s go through some steps to help you troubleshoot and resolve this problem:
Network Connectivity: First, ensure that both your PC and the Verdin development board are on the same network and can communicate with each other. You can verify this by pinging the Verdin board from your PC and vice versa.
Port Accessibility: Check that the necessary ports are open and accessible between your PC and the Verdin board. Specifically, ensure that port 2375 (used by Docker) is open on the Verdin board and that your local registry port (5002) is accessible from the board.
Docker Daemon Configuration: Verify that the Docker daemon on your PC is configured to allow connections from the Verdin board. This might involve adjusting firewall settings or Docker’s configuration to permit external access.
Local Registry Setup: If you are using a local Docker registry on your PC, ensure it is correctly configured and running. Check that the registry is not marked as insecure unless you have explicitly configured Docker to allow insecure registries.
WSL2 Configuration: Make sure that your Visual Studio Code is correctly connected to the WSL2 environment. Open a WSL2 terminal and launch VS Code from there to ensure proper integration.
Internal Logs and Errors: Review the internal logs in Visual Studio Code for any additional error messages that might provide more context. Use the “Developer: Toggle Developer Tools” option in the command palette to access these logs.
Network Stability: Consider the possibility of network instability or low bandwidth affecting the connection. If this is a recurring issue, you might need to investigate your network setup or consider using a pull-through cache to reduce network load.
By following these steps, you should be able to identify and resolve the cause of the timeout issue during your Docker deployment process. If the problem persists, further investigation into specific error messages and logs will be necessary to pinpoint the exact cause.
I hope this helps you get back to smooth deployments.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
Seems like there was an issue with the Verdin i.MX8MP device trying to pull/access the container images from the local registry hosted on your PC at http://192.168.1.205:5002/.
This usually indicates some network related issue. Sometimes office/corporate network setups have firewalls or other network configurations that can interfere with our VSCode extension. Make sure the Verdin i.MX8MP can reach 192.168.1.205 and that the port 5002 is also available on your PC.
If this was working until recently, like you said. Then this could indicate something in your network environment may have changed recently and is now disrupting this process.
Another thing this could be is an issue with the Docker installation on your PC. Make sure you only have Docker Desktop or Docker engine in WSL2 installed, not both at the same time. Preferably Docker Engine in WSL2, I’ve seen with other users Docker Desktop can sometimes break our VSCode extension with new versions/updates.
Beyond this I can’t really give anything more specific since the error just indicates a general network issue, which could be caused by many things in your environment. I can say that deployment does seem to work on my side, so I don’t believe this is a bug in the VSCode extension.
