This issue is a: (mark with an x)
Issue description
The Azure Container Apps Portal rejects valid container image digest references in params.json with a client-side validation error. Currently, only image tags are supported, which leads to incorrect image pulls when tags are reused.
Steps to reproduce
- Create a Container App deployment configuration
- Reference the image as
registry/repository@sha256:<digest> instead of just registry/repository:tag
- Attempt to deploy through the Portal
- Observe the validation error from the Portal
Expected behavior
The Portal should accept both notations:
registry/repository:tag (currently works)
registry/repository@sha256:<digest> (should work)
Actual behavior
Client-side validation rejects digest-based references. The error message indicates that only tag notation is supported, causing image pull failures.
Error Message
Container was terminated with exit code 27 and reason 'ImagePullFailure'.
Pull image: registry/repository@sha256:... failed with exit code 1
This issue is a: (mark with an x)
Issue description
The Azure Container Apps Portal rejects valid container image digest references in
params.jsonwith a client-side validation error. Currently, only image tags are supported, which leads to incorrect image pulls when tags are reused.Steps to reproduce
registry/repository@sha256:<digest>instead of justregistry/repository:tagExpected behavior
The Portal should accept both notations:
registry/repository:tag(currently works)registry/repository@sha256:<digest>(should work)Actual behavior
Client-side validation rejects digest-based references. The error message indicates that only tag notation is supported, causing image pull failures.
Error Message