Updates fail in Torizon - no route to host registry-1.docker.io

Technical Support
, ,
1

Hi All,

I get this error when trying to install chromium
Get “https://registry-1.docker.io/v2/torizon/chromium/manifests/sha256:<-snipped->”: dial tcp [2600:1f18:2148:<-snipped->]:443: connect: no route to host

I see the error in the cosole after running sudo journalctl -f -u aktualizr* and then attempting to install chromium via the Torizon portal

How can this be fixed?
I am able to perform Torizon install over my network, so I don’t suspect I have any loacal networking issues.

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:

Hello,

The error message you’re encountering, “no route to host,” typically suggests a network connectivity issue between your device and the Docker registry. Here are some steps you can take to troubleshoot and potentially resolve this issue:

  1. Network Configuration: Double-check that your device is properly connected to the network. Ensure that the network settings, such as IP address, gateway, and DNS, are correctly configured.

  2. Test Connectivity: Use tools like ping or traceroute to test connectivity to external servers. For instance, try ping google.com to verify internet access.

  3. DNS Resolution: Confirm that your device can resolve domain names. You can test this by using the nslookup or dig command to resolve registry-1.docker.io.

  4. Firewall and Security Settings: Ensure there are no firewall rules or security settings blocking outbound connections on port 443 (HTTPS).

  5. IPv6 Configuration: The error message includes an IPv6 address. If your network does not support IPv6, you might need to disable it or ensure proper configuration. This can be done by editing network settings or using the sysctl command to disable IPv6 temporarily.

  6. Proxy Settings: If your network uses a proxy, make sure your device is configured to use it. You can set proxy settings in the Docker configuration or system-wide.

  7. Docker Configuration: Verify that Docker is correctly configured on your device. Check the Docker daemon logs for any additional error messages that might provide more context.

If these steps do not resolve the issue, consider testing the network connection from another device on the same network to rule out device-specific problems.

I hope this helps you resolve the issue. If you have any further questions, feel free to ask.

Best regards,
Toradex AI Assistant.

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

GPU performance in Chromium container on Torizon OS iMX8M-Plus.

3

Hi @chad.au,

I know you said you don’t suspect a network issue, but the log line you shared would indicate otherwise.

As a sanity test, what happens when you try to manually docker pull that container image onto that device from the command-line? Does it work, or dies it similarly fail?

It could be your network for some reason can’t access Docker Hub where this container image is located.

Best Regards,
Jeremias