Debugging not possible because board can not find docker image in registry

Technical Support
, , , ,
2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

The issue you’re encountering seems to be related to the mismatch between where the container image is being pushed and where it’s being pulled from. Here are a few steps to troubleshoot and potentially resolve the issue:

  1. Check Image Tagging: Ensure that the image is tagged correctly with the IP address of your host PC (10.131.90.37:5002) before pushing it to the local registry. You can do this by using the docker tag command:

    docker tag mycobot-toradex-debug:latest 10.131.90.37:5002/mycobot-toradex-debug:arm64

  2. Push to the Correct Registry: After tagging, push the image to the local registry:

    docker push 10.131.90.37:5002/mycobot-toradex-debug:arm64

  3. Verify Local Registry Configuration: Ensure that your local registry is set up correctly and is accessible from the Verdin board. You might need to configure Docker to allow communication with an insecure registry if TLS is not set up:

    • Modify the Docker daemon configuration on the Verdin board to allow the insecure registry by editing /etc/docker/daemon.json:
      {
  "insecure-registries" : ["10.131.90.37:5002"]
}
    • Restart the Docker service after making changes.

  4. Check Docker Compose Configuration: Ensure that your docker-compose.yml file is correctly referencing the image with the full registry path:

    services:
  mycobot-toradex-debug:
    image: 10.131.90.37:5002/mycobot-toradex-debug:arm64

  5. Rebuild and Push the Image: If the image was initially built with a different tag, you might need to rebuild it with the correct tag and push it again.

By ensuring that the image is correctly tagged and pushed to the local registry, and that the Verdin board is configured to pull from this registry, you should be able to resolve the issue. If the problem persists, double-check network connectivity between the host PC and the Verdin board, and ensure there are no firewall rules blocking access.

Please, also check if these links can help you solve your problem:

Issue with TorizonCore builder.