Hi @Zach Howell ,
Thanks for the offline conversation.
I am summarizing the discussion and posting as answer.
Upon investigating further, the error occurred when using User Assigned Managed identity with registries in yaml.
As a workaround, followed below steps to achieve the requirement.
- Created a Container App using Azure CLI and enabled System Assigned Managed identity in portal.
- Navigate to Container registries and assign
ACR PULLrole to container app's managed identity.
Command:
az role assignment create --assignee <ContainerAppSystemIdentityPrincipalID> --role AcrPull --scope /subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroup>/providers/Microsoft.ContainerRegistry/registries/<ACRName>
- Explicitly configured the registries section with the
identity: systemin theyaml. This tells Azure Container Apps to use the system-assigned managed identity for authenticating to the ACR.
properties:
configuration:
ingress:
external: true
allowInsecure: false
targetPort: 80
registries:
- server: myregistry.azurecr.io
identity: system
template:
containers:
- image: mcr.microsoft.com/azuredocs/containerapps-helloworld:latest
name: app
resources:
cpu: 0.5
memory: 1Gi
Hope it helps!
Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you.