Azure Container Registry gives UNAUTHORIZED error, running az acr health-check gives HELM_COMMAND_ERROR

Iñigo Paños Basterra 20 Reputation points
2024-05-14T09:50:24.03+00:00

Trying to push images as owner into a newly created Azure Container Registry keeps giving Unauthorized error. Checked and no typos, credentials seemed fine. Looking for help I found az acr health-check and it gave me a HELM_COMMAND_ERROR, which I saw here https://learn.microsoft.com/en-us/azure/container-registry/container-registry-health-error-reference#helm_command_error means Helm client cna't be found and to check it is installed. I don't even know what it is so any help on this matter is appreciated.

Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
407 questions
{count} votes

Accepted answer
  1. vipullag-MSFT 25,121 Reputation points
    2024-05-14T10:23:18.24+00:00

    Hello Iñigo Paños Basterra

    Welcome to Microsoft Q&A Platform, thanks for posting your query here.

    ACR is temporarily pausing ACR Tasks runs from Azure free credits. Refer: https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tasks-overview#what-is-acr-tasks

    If your subscription is a free trail this could be the reason why this is failing.

    User's image

    The HELM_COMMAND_ERROR error message you are seeing indicates that the Azure CLI is unable to find the Helm client. This could be because the Helm client is not installed on your machine or the path to the Helm client is not added to the system environment variables.

    To resolve this issue, you can try installing the latest version of the Helm client and adding its path to the system environment variables. You can download the latest version of the Helm client from the official Helm website.

    Once you have installed the Helm client, you can add its path to the system environment variables.
    After adding the path to the Helm client, you can try running the az acr health-check command again to see if the issue has been resolved.
    Hope this helps.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful