az containerapp up expects container registry to be in the same subscription

[Thorstensen]

Related command

az containerapp up --name containerAppName --registry-server myRegistry.azurecr.io \
                   --registry-user myUser --registry-password myPassword \
                   --image myRegistry.azurecr.io/myApp/backend:$(Build.BuildId)

Describe the bug
Running the command above expects that ACR is in the current subscription, even though the FQDN to ACR is provided with correct credentials. In our current set up, we have one Azure Container Registry in Subscription Production, but we want to create resources in Subscription Test

To Reproduce

1. Make sure that you have two subscriptions in Azure. One where the ACR is located, and one subscription where the ContainerApp should be created.
2. Install the Azure CLI and containerapp extension by running az extension add --name containerapp --upgrade
3. Open you terminal of choice, and run the command above reflecting your environment.

Expected behavior
The ContainerApp will be created in Subscription Test based on the specified image from ACR in Subscription Production

Environment summary

azure-cli: 2.43.0
containerapp 0.3.20

Additional context

• According to this issue the flag --subscription can be set, but this will also create the resources in this subscription.
• According to this issue it works when the image is located in DockerHub - I can not see any differences between these to image repositories.

[yonzhan]

route to CXP team

[Thorstensen]

To elaborate: Running az containerapp up specifying --registry-server --registry-user and --registry-password result in ERROR: The resource with name 'xyz' and type 'Microsoft.ContainerRegistry/registries' could not be found in subscription 'mySubscription (Some-guid-identifying-subscription)'. These two resources ARE in two different subscriptions, but why does that matter when all the information above is supplied?

[SaurabhSharma-MSFT]

@Thorstensen Can you please look into this GitHub issue. Also, refer to the below documentation if this helps to achieve what you are looking for.

• My ACR and Webapp are in in a different subscription

[ghost]

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

[phoenixx]

I am also seeing this exact issue. A container image from a registry in Subscription A is not accessible when attempting to use az containerapp up in Subscription B - I get the exact same error as above: "ERROR: The resource with name 'xyz' and type 'Microsoft.ContainerRegistry/registries' could not be found in subscription 'mySubscription (Some-guid-identifying-subscription)'."

I have been able to use Terraform (with the azure/azapi provider) to initially deploy the Azure Container App successfully and then az containerapp update to deploy new image versions, but this is far from ideal.

Is there any further information I can provide to help get to a solution?

[ghost]

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

[giovannifl]

Please reopen ths ticket again because it has not been fixed and it is still relevant

[glennsdavis]

This was working for me but is no longer not working.

1.) Using "az containerapp create" command, create container app in Subscription A from image in Azure Container Register in Subscription B.

2.) Using "az containerapp up" command, update same container app in Subscription A from image in Azure Container Register in Subscription B.

#2 now returns error "type 'Microsoft.ContainerRegistry/registries' could not be found in subscription".