-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Azure/CLI@V1 Error on Self-Hosted Runner on Azure AKS #116
Comments
Hi @moulidz, |
Hi @MoChilia, Sure. I will also test on my side with different configurations and update here if i find anything. |
Hello @MoChilia , This may be related. I am also getting an error when running the agent from an attached disk in Azure. The agent runs on a Linux VM from a mounted drive at
Hope this helps either reproduce it or narrow down the root cause |
Hi, I tried the az cli action from a new self-hosted runner using the github arc runner. Got a different error here:
Thanks |
I face the same issue with for the workaround, I'm installing azure cli on every action run & using it |
Hi @vijayrajah, you can try running - name: Azure CLI Action
uses: azure/cli@v2
with:
azcliversion: latest
inlineScript: |
az login --service-principal --username ${{ secrets.AZURE_CLIENT_ID }} --password ${{ secrets.AZURE_CLIENT_SECRET }} --tenant ${{ secrets.AZURE_TENANT_ID }}
az account set --subscription ${{ secrets.AZURE_SUBSCRIPTION_ID }} |
Hi,
I am facing an error while using Azure/CLI@V1 on my self-hosted runner on Azure Kubernetes Service.
The error:
ERROR: Please run 'az login' to setup account.
Error: Error: az cli script failed.
CLi version: 2.52.0 pre-installed on the AKS actions-runner image along with Azure powershell modules.
The Azure/Login@V1 is successful and Azure/Powershell@V1 is also successful. Only the Azure/CLI@V1 has the error.
On inspecting the docker image for the CLI, I found that the .azure folder is empty.
When I run the same workflow on an Azure VM self-hosted runner instead of AKS, the Azure/CLI@V1 works and it is the same version - 2.52.0
Is the error because of the latest version of CLI? Should I revert to 2.30.0?
Thanks
Mouli
The text was updated successfully, but these errors were encountered: