InvalidParameterValueInContainerTemplate - deploy quickstart image in portal with VNet

[donaldtse118]

Please provide us with the following information:

This issue is a: (mark with an 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

When I deploy the first ContainerApp with quickstart image thru azure portal ... I got the following error..

The following field(s) are either invalid or missing. Field 'template.containers.simple-hello-world-container.image' is invalid with details: 'Invalid value: "mcr.microsoft.com/k8se/quickstart:latest": Get "https://mcr.microsoft.com/v2/": EOF';. (Code: InvalidParameterValueInContainerTemplate)

Steps to reproduce

1. Setup Container App environment with workload profile, bind with VNet
2. Create Container App on this environment with quick start setting

Expected behavior Successfully deploy quickstart app and able to access homepage

Actual behavior failed to start deploying as claimed template error

Screenshots

Additional context

• error in Portal, without manually specific template
• my ContainerApp environment detail
  • with workload consumption profile as my organization setup UDR
  • bind to a VNet (with custom DNS)
• Tried export the ARM template and converting it to yaml. Then deploy with az cli command to another environment in the consumption plan only and with VNet binding, could successfully deploy
• same comment run on the environment (workload profile+VNet binded got same InvalidParameterValueInContainerTemplate error as portal)

[donaldtse118]

Finally I found it is related network traffic block to image repository. It will be nicer if the error message could give more hints.
Thank you for your time.

[cachai2]

@donaldtse118 I'm glad to hear that the issue was resolved. Can you share what kind of error messaging you would have liked to see during your investigation? Something like, "The image repository isn't accessible"?

[sch1ldkr0ete]

@cachai2 we also just ran into this error and it took us a while to figure out that the problem was caused because of a firewall.

Something like, "The image repository isn't accessible"?

That would be nice! It would have saved us a lot of time :)