Torizoncore-builder --login-to not Working

[ToradexAI]

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

Did you like my answer?

---

Hello Philippe,

Thank you for reaching out with your question. It seems you’re encountering an issue with pulling your application container from a private registry using Torizon Platform, despite being able to manually log in and pull the container on the device. This suggests a problem with how the credentials are being handled by the Torizon Platform.

Here are some steps to troubleshoot and resolve this issue:

1. Verify Credentials: Double-check that the credentials used with the --login-to option are correct and have the necessary permissions to access the private registry. Ensure the token’s scope and permissions on GitHub are set appropriately.

2. Credential Deployment: The Torizon Platform requires credentials to be accessible during automated updates. You can use the TorizonCore Builder tool to embed these credentials into the TorizonCore image. This involves using docker login on a device to create a config.json file in /etc/docker, then capturing this configuration with TorizonCore Builder to create a custom image.

3. Custom TorizonCore Image: Once you have a custom TorizonCore image with the embedded credentials, deploy this image to your devices. This ensures that all devices have the necessary credentials pre-provisioned.

4. Check Aktualizr Logs: Review the logs from Aktualizr for any additional error messages or clues that might indicate why the authentication is failing. This can provide insights into whether the issue is with the credentials or the network configuration.

5. Network Configuration: Ensure there are no network restrictions or firewall settings that might be blocking access to the registry from the device.

By following these steps, you should be able to resolve the unauthorized error and successfully pull your application container from the private registry using Torizon Platform. If the issue persists, consider revisiting the credential setup and deployment process to ensure all steps are correctly followed.

I hope this helps! Please feel free to reach out if you have any more questions.

Best regards,
Toradex AI Assistant

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

Imx8x Torizon 5.7.2 to 6.3 Upgrade Journey - permissions on /etc/docker wrong on update

Hi, This is a brief note to report that after you follow the process of updating imx8x modules from 5.7.2, there seems to be some missing files and ownership/permission issues with /etc/docker. Step 1. With docker desktop etc up and running, grab a container from my repo torizon@colibri-imx8x-00000000:~$ docker pull XXXX/XXXXXXX Using default tag: latest Error response from daemon: pull access denied for XXXX/XXXXXXX, repository does not exist or may require 'docker login': denied: requested …

OTA issues from Torizon Platform and Github Actions

Hi, I am getting a failed build on the github actions which says: Status: Downloaded newer image for torizon/torizoncore-builder:early-access You are running an early access version of TorizonCore Builder. An unexpected Exception occured. Please provide the following stack trace to the Toradex TorizonCore support team: Traceback (most recent call last): File "/builder/torizoncore-builder", line 221, in <module> mainargs.func(mainargs) File "/builder/tcbuilder/cli/platform.py", line 5…

Torizon cloud update fails, docker login fails.