Open stan-spotts opened 4 months ago
Hi @stan-spotts,
2.59.0 is not the latest Azure CLI(2.60.0).
If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.
Hi @stan-spotts Find similar issue https://github.com/Azure/azure-cli/issues/18596. | ||
---|---|---|
Issue title | Azure Pipeline issue with AzureCLI Task failing when accessing Container Group | |
Create time | 2021-06-22 | |
Comment number | 3 |
Please confirm if this resolves your issue.
Thank you for opening this issue, we will look into it.
Hi @stan-spotts,
2.59.0 is not the latest Azure CLI(2.60.0).
If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.
Same error with 2.60.0
azure-cli 2.60.0
core 2.60.0
telemetry 1.1.0
Extensions:
ssh 2.0.3
Dependencies:
msal 1.28.0
azure-mgmt-resource 23.1.0b2
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\stanadm\.azure\cliextensions'
Python (Windows) 3.11.8 (tags/v3.11.8:db85d51, Feb 6 2024, 22:03:32) [MSC v.1937 64 bit (AMD64)]
Legal docs and information: aka.ms/AzureCliLegal
@stan-spotts is your issue resolved? i am also getting the same error when i am trying to create azure container instances using yaml file , Please check the image and registry credential
@Subham0793 No, it never worked. I gave up on it. The image worked fine to push to an Azure App Service in a GitHub Action, btw, using same credentials for ACR access.
Describe the bug
I'm trying to use GitHub Actions to build a container, push it to an Azure Container Registry, then create an Azure Container Instance from it. Creating the image in the ACR works just fine. But when I try to use azure container create, using the exact same registry credentials, I get the error that the container group is not accessible and "Please check the image and registry credential."
If I run the command from my laptop and the image exists I get the same error and reporting that here. Hoping, however, that someone also has a clue why it fails in GitHub Actions.
Related command
az container create -g $resGroup --name $appName --image "$acrName/$appName:6b708baf66bd1bfcf2442954aea84778df4181e1' --registry-login-server $acrName --registry-username $reg_username --registry-password $reg_password --ip-address Private --vnet $vnet --subnet $subnet --ports 443 --location eastus
Errors
cli.azure.cli.core.azclierror: (InaccessibleImage) The image 'cgfnscr.azurecr.io/integration-api:6b708baf66bd1bfcf2442954aea84778df4181e1' in container group 'integration-api' is not accessible. Please check the image and registry credential. Code: InaccessibleImage Message: The image 'cgfnscr.azurecr.io/integration-api:6b708baf66bd1bfcf2442954aea84778df4181e1' in container group 'integration-api' is not accessible. Please check the image and registry credential. az_command_data_logger: (InaccessibleImage) The image 'cgfnscr.azurecr.io/integration-api:6b708baf66bd1bfcf2442954aea84778df4181e1' in container group 'integration-api' is not accessible. Please check the image and registry credential. Code: InaccessibleImage Message: The image 'cgfnscr.azurecr.io/integration-api:6b708baf66bd1bfcf2442954aea84778df4181e1' in container group 'integration-api' is not accessible. Please check the image and registry credential.
Issue script & Debug output
Expected behavior
I expected the container instance would be created
Environment Summary
Additional context
The ACR is in a subnet (10.5.0.0/27) which has a private endpoint configured. The ACI is to be deployed to another subnet (10.5.0.64/29) which doesn't yet have a private endpoint (it will, and the API's will be exposed via APIM) and is delegated to Microsoft.ContainerInstance/containerGroups.
FWIW. the github workflow yaml is this, and the first part does indeed deploy to the container and as you can see uses the same credentials as specified in the az container create call. Using az call directly as the github action is woefully outdated and not being actively worked on, doesn't support vnet, subnet, etc.