Torizon:pull-container-torizon-debug-arm64 failed.

Technical Support
1

Hi Team,

Module : Verdim AM62
Carrier Board : Verdin Development board
Host OS : Winddows

I’m able to setup the build environment for torizon and able to connect the target device by following the installation wizard in Visual Studio code, specified in the video.

I tried to run and debug a sample python hello-world program. But I’m getting the following error.

  • Executing task: DOCKER_HOST=192.168.0.131:2375 LOCAL_REGISTRY=192.168.0.110 TAG=arm64 GPU=-am62 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose pull quickstart-debug

WARN[0000] The “DOCKER_LOGIN” variable is not set. Defaulting to a blank string.
[+] Pulling 1/1
! quickstart-debug Warning Get "http://192.168.0… 30.3s
WARNING: Some service image(s) must be built from source by running:
docker compose build quickstart-debug
1 error occurred:
* Error response from daemon: Get “http://192.168.0.110:5002/v2/”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

  • The terminal process “/usr/bin/bash ‘-c’, ‘DOCKER_HOST=192.168.0.131:2375 LOCAL_REGISTRY=192.168.0.110 TAG=arm64 GPU=-am62 DEBUG_SSH_PORT=6502 DEBUG_PORT1=6512 DEBUG_PORT2= DEBUG_PORT3= docker compose pull quickstart-debug’” terminated with exit code: 1.
  • Terminal will be reused by tasks, press any key to close it.

Kindly help me to solve this issue.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

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

Hello,

I see you’re encountering a Docker registry timeout issue when trying to debug your Python application on the Verdin AM62. This is a network connectivity problem between your Verdin board and the local Docker registry on your Windows host machine.

Root Cause Analysis

The error indicates that your Verdin AM62 board (IP: 192.168.0.131) cannot reach the local Docker registry running on your Windows host (IP: 192.168.0.110) at port 5002(1)(2). The timeout occurs when the board tries to pull the container image from your local registry.

Troubleshooting Steps

1. Network Connectivity Verification

  • Ensure both your Windows host (192.168.0.110) and Verdin AM62 board (192.168.0.131) are on the same network(1)(2)
  • Test connectivity by pinging the board from your PC and vice versa(1)
  • Verify that port 5002 is accessible from the Verdin board to your Windows host(1)(2)

2. Firewall and Port Configuration

  • Check Windows Firewall settings to ensure port 5002 is allowed for incoming connections(1)
  • Verify that no corporate firewall or network configuration is blocking the connection(1)(2)
  • Ensure the Docker daemon on your Windows host is configured to allow connections from the Verdin board(1)

3. Docker Registry Configuration

  • Confirm that your local Docker registry is running and accessible at http://192.168.0.110:5002(1)(2)
  • Test registry accessibility from another machine on the same network using a web browser or curl(1)
  • If using an insecure registry, ensure the Docker daemon on the Verdin board is configured to allow connections to insecure registries(1)

4. Network Environment Considerations

Since you mentioned this was working before, check if anything changed in your network environment recently(1). Office or corporate network setups often have firewalls or other configurations that can interfere with the Torizon IDE Extension(1)(2).

5. Docker Installation Verification

Ensure you have only one Docker installation - either Docker Desktop or Docker Engine, not both simultaneously(1). Docker Engine is generally preferred for use with the Torizon IDE Extension.

Additional Recommendations

  • If you’re using a direct Ethernet connection between your host and the Verdin board, verify that the board can properly route to your host’s registry endpoint(2)
  • Consider increasing Docker timeout settings if network latency is a concern(1)
  • Check that the necessary ports (2375 for Docker daemon, 5002 for registry) are properly configured and accessible(1)(2)

The deployment process should work correctly once the network connectivity issue between your Verdin AM62 board and the local Docker registry on your Windows host is resolved.

Best regards, Toradex AI Assistant.

3

Hey, @Meenakshy,

The AI answer looks good to me, the error message indicates a network issue. Can you try the suggestions it gave? In particular, this other community post looks relevant to me. Feel free to ask me if you encounter any issues.

Best regards,