Verdin IMX8MP - Deploying Docker Containers for Debug Using the Torizon IDE: Failing at docker pull

Thanks for your response.

Please remember to tick the “Solution” checkbox below if my response solves your question. If you have follow-up questions, just continue to tag me using @ToradexAI in your new posts.

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


Thank you for your update, Andrew.

The key detail now is that curl http://localhost:5002/v2/ returns {}, but curl http://172.16.16.57:5002/v2/ does not—this shows the registry is running, but only bound to localhost (127.0.0.1), not all interfaces (0.0.0.0). Therefore, it is not reachable using the machine’s IP, which is required by Torizon IDE and your target device.

To address this, please follow these steps:

  1. Stop the Existing Registry
    First, stop and remove the currently running registry container. You can find its container ID or name using:
docker ps | grep 5002

Then stop and remove it:

docker stop <container-id-or-name>
docker rm <container-id-or-name>
  1. Launch the Registry Bound to All Interfaces
    Now, start a new registry container with explicit binding to 0.0.0.0:
docker run -d -p 5002:5002 --restart always --name registry -e REGISTRY_HTTP_ADDR=0.0.0.0:5002 registry:2

This ensures the registry is accessible from both localhost and your machine’s IP address.

  1. Verify Accessibility
    Check that it’s running with:
docker ps | grep 5002

And check from both your development machine and from your IMX8MP:

curl http://localhost:5002/v2/
curl http://172.16.16.57:5002/v2/

Each should return {}.

  1. Update Docker Daemon (on the Target)
    On your IMX8MP, make sure /etc/docker/daemon.json includes (update IP as needed):
{
  "insecure-registries" : ["172.16.16.57:5002"]
}

See: Store and Share Container Images | Toradex Developer Center

Then, restart the Docker service:

sudo systemctl restart docker
  1. Restart VS Code and Torizon Extension
    Close and reopen VS Code on your development PC, and re-initiate the deployment/debug workflow.

After these steps, both your PC and IMX8MP should be able to reach the registry via http://172.16.16.57:5002/v2/, resolving the deployment issue.

For more, see:

If you encounter further issues, please share which step fails and any console output.

Best regards, Toradex AI Assistant.