Error while publishing asp .net core 3.1 web app from docker image from docker hub to azure web container service.

[vivek781113]

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 593c3abc-7b38-6673-62b6-7787d0dda4dd
Version Independent ID: cbb2b875-b220-596c-7b4d-c2cf6c644335
Content: Deploy a Docker container app - Azure Pipelines
Content Source: docs/pipelines/apps/cd/deploy-docker-webapp.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

Tried out all the suggestion but no luck as of now. Please find the container logs of the app service.

2020-09-02T17:48:32.007Z INFO - Pull Image successful, Time taken: 0 Minutes and 35 Seconds
2020-09-02T17:48:32.068Z INFO - Starting container for site
2020-09-02T17:48:32.069Z INFO - docker run -d -p 8166:80 --name thintankcoreapi_0_5aec585a -e WEBSITES_ENABLE_APP_SERVICE_STORAGE=false -e WEBSITE_SITE_NAME=thintankcoreapi -e WEBSITE_AUTH_ENABLED=False -e PORT=80 -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=thintankcoreapi.azurewebsites.net -e WEBSITE_INSTANCE_ID=2a1ab72b2d9ad013ac740eb676404cb06c512c8203547cc3d3c76b3dfea53aee -e HTTP_LOGGING_ENABLED=1 vivek781113/corebase31

2020-09-02T17:48:35.526Z INFO - Initiating warmup request to container thintankcoreapi_0_5aec585a for site thintankcoreapi
2020-09-02T17:48:36.196Z ERROR - Container thintankcoreapi_0_5aec585a for site thintankcoreapi has exited, failing site start
2020-09-02T17:48:36.198Z ERROR - Container thintankcoreapi_0_5aec585a didn't respond to HTTP pings on port: 80, failing site start. See container logs for debugging.
2020-09-02T17:48:36.210Z INFO - Stopping site thintankcoreapi because it failed during startup.

Originally posted by @vivek781113 in #46401 (comment)

[himanshusinha-msft]

Thanks for the ask . At this time we are reviewing the ask and we will reply back as soon as we can .

[AjayKumar-MSFT]

@ Vivek, As I understand you have tried all the steps from the referenced thread, but it is still not working. I wish to engage with you offline for a much closer look and provide specialized assistance, please send an email with subject line “Attn:Ajay” to AzCommunity[at]Microsoft[dot]com referencing this thread, Azure subscription ID, WebApps name, I will follow-up with you.

As we will work offline, we will close this out, but if you feel you need more information please just let us know.

[irving-caamal]

Hi guys, I've been facing this issue for a couple of days, and finally, I got a solution, I've created a detailed repository that specifies some of the problems that I resolved for my basic node.js application., hope it can help someone, 'cause this was a little bit confusing

[AjayKumar-MSFT]

irvv17, Thanks for sharing the solution that worked for you with the community. Apologies for all the confusion. We'll work on adding additional clarity/with author's review.