[X] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)
Issue description
I have a internal container app which uses admin credentials to connect to ACR deployed via Azure Pipelines. Deploying appears to go successful using Bicep template "Microsoft.App/containerApps@2023-05-01". However, during activation stage, it reports failure on "Container 'testservice' was terminated with exit code '' and reason 'ImagePullFailure'"
Steps to reproduce
Create an ACR with public access
Create container app environment with consumption profile attached to a vnet
Deploy Container App throug Bicep using "Microsoft.App/containerApps@2023-05-01" with UserName / Password for registry access
Expected behavior
Revision to have gone in to running state
Actual behavior
Revision reported as "Activation failed"
Screenshots
Screenshot from log:
Additional context
Happens on initial revision deployed through bicep and also when any further revisions deployed through AzureContainerApps@1
This issue is a: (mark with an x)
Issue description
I have a internal container app which uses admin credentials to connect to ACR deployed via Azure Pipelines. Deploying appears to go successful using Bicep template "Microsoft.App/containerApps@2023-05-01". However, during activation stage, it reports failure on "Container 'testservice' was terminated with exit code '' and reason 'ImagePullFailure'"
Steps to reproduce
Expected behavior Revision to have gone in to running state
Actual behavior Revision reported as "Activation failed"
Screenshots
Screenshot from log:
Additional context
Happens on initial revision deployed through bicep and also when any further revisions deployed through AzureContainerApps@1