Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hi Ahmed49,
Based on the context provided, it seems like you’re encountering an issue with accessing a container image from your Azure Container Registry (ACR) using the TorizonCore Builder tool. The error message indicates that the image he-varia-torizon is not found or access is denied, which could be due to a few reasons:
Repository Name: Double-check the repository name in your Azure Container Registry. Ensure that he-varia-torizon is the correct name and that it exists in your registry.
Authentication: Make sure that you have successfully authenticated with the Azure Container Registry. You mentioned that the username and password are correct, but it’s worth verifying that the authentication tokens are correctly set up on your host machine as per the steps outlined in the context.
Docker Login: The error message suggests that a docker login might be required. Ensure that you have logged in to your Azure Container Registry using Docker on your host machine. You can do this by running:
docker login registryName.azurecr.io
Use your Azure credentials to authenticate.
Image Tag: Verify that the tag latest exists for the image he-varia-torizon. If the image is tagged differently, you need to specify the correct tag in your docker-compose.yml file.
Network Issues: Ensure there are no network issues preventing access to the Azure Container Registry.
If you’ve checked all the above and the issue persists, you might want to look into the Torizon Cloud Web Interface for more detailed logs or error messages that could provide further insights.
Best regards,
[Your Name]
Please, also check if these links can help you solve your problem:
Can you give the complete output out the torizoncore-builder bundle command?
Also, we recommend using the torizoncore-builder build command instead of the torizoncore-builder bundle command.
In the tcbuild.yaml configuration file, you can set the info for the container registry under the output/easy-installer
# bundle:
# >> Choose one of the options:
# >> (1) Specify a docker-compose file whose referenced images will be downloaded.
# >> Properties platform, username, password, registry and ca-certificate are optional.
# compose-file: files/docker-compose.yml
# platform: linux/arm/v7
# username: "${USERNAME}"
# password: "${PASSWORD}"
# registry: hub.docker.com
# ca-certificate: cacert.pem
I think you probabluy found the same issue that I described here.
The scripts should be changed to work with ACR, because the syntax is different from dockerhub.