This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 3%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENK%3C/text%3E%3C/svg%3E)
I have deployed the docker image of a .net core Microservice via Azure container registry into the Azure container apps
am facing the bellow issues after creating the container app is created
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Hard to say without looking at the logs. Can you share the logs please,
Monitor an app in Azure Container Apps
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 0%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFV%3C/text%3E%3C/svg%3E)
Make sure your target port for ingress traffic is set to 8080
Note the breaking change.
Default ASP.NET Core port changed from 80 to 8080
https://learn.microsoft.com/en-us/dotnet/core/compatibility/containers/8.0/aspnet-port
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 63%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYA%3C/text%3E%3C/svg%3E)
Thanks, @Francisco Vilches that works for me.
The target port wasn't set right in Ingress. because of it the page was loading for a long time. and wrt revision, it was failing for few and working for few
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 76%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBP%3C/text%3E%3C/svg%3E)
Same problem here! Sometimes the status of the revision is shown as "Faile222756-containerappconsolelogs-cl.txtd" and sometimes "Provisioned". The endpoint is never reachable (same as the screenshots above).
Nevermind! My problem was because of an faulty container image. @Narasimman, Karthigai Lakshmi : Test thouroughly whether you container images also work locally ;)