Container images download failed from Azure Container Registry

Hi Toradex,

I want to run the torizoncore-builder bundle command

torizoncore-builder bundle docker-compose-he-varia-torizon.yml --login-to --bundle-directory bundle

my-azure-container-regitry = registryName.azurecr.io
username is correct
password is correct

But. it fails with the following error:

Error: container images download failed: 404 Client Error for https://x.x.x.x:22376/v1.40/images/create?tag=latest&fromImage=he-varia-torizon: Not Found (“pull access denied for he-varia-torizon, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied”)

Here how the docker-compose.yml file loks like when I 'am calling the image he-varia-torizon:latest

Info: The docker image is already has been pushed to the Azure Registry.
Also manually , I could pull any docker image from the Azure registry.

docker-compose-he-varia-torizon.yml (1.4 KB)

Any help?

Best regards,
Ahmed49

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

Did you like my answer?

:+1: :-1:


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:

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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:

Issue with TorizonCore builder.

Hi @Ahmed49

Just to make sure, but are you passing the parameters to --login-to?
The complete command should be

torizoncore-builder bundle docker-compose-he-varia-torizon.yml --login-to <repository-url> <username> <password> --bundle-directory bundle

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.

Hello @Ahmed49,

Were you able to get this issue resolved?

Best Regards,
Bruno

Hi @bruno.tx
Yes, it’s resolved, I 'am using a script to call the bundle command with the switch --login-to.

Best regards,
Ahmed 49

Hi @allan.tx

Yes, I 'am using then switch --login-to, passing also the correct params

Bets regards,
Ahmed49

Thanks for the update @Ahmed49.

Best Regards,
Bruno