did not start within expected time limit ?

Description

https://stackoverflow.com/questions/52823025/azure-container-did-not-start-within-expected-time-webapp

https://stackoverflow.com/questions/52823025/azure-container-did-not-start-within-expected-time-webapp
Azure: Container did not start within expected time (WebApp)
To solve (1) I set WEBSITES_CONTAINER_START_TIME_LIMIT to 1800 (which is the max) To solve (2) I set WEBSITES_PORT (in app setting) with a value of 80 to expose that port. (As per documentation) Any others things I should try ? PS the default docker log file outputs the following:

https://serverfault.com/questions/1003418/azure-docker-app-error-site-did-not-start-within-expected-time-limit-and-co

https://serverfault.com/questions/1003418/azure-docker-app-error-site-did-not-start-within-expected-time-limit-and-co
Azure: Docker App Error …site did not start within expected time limit …
Azure: Docker App Error …site did not start within expected time limit and Container X didn’t respond to HTTP pings on port 80 Ask Question Asked 3 years, 9 months ago Modified 3 years, 9 months ago Viewed 12k times 2 I have a Flask Python app that is run via Gunicorn from a Docker Linux container.

https://techcommunity.microsoft.com / t5 / apps-on-azure-blog / things-you-should-know-web-apps-and-linux / ba-p / 392472

https://techcommunity.microsoft.com / t5 / apps-on-azure-blog / things-you-should-know-web-apps-and-linux / ba-p / 392472
Things You Should Know: Web Apps and Linux
However, at the end of the log, we see a message that the container did not start within the expected time limit. Notice in the next to the last line that the Node.js engine is listening on port 3000. The problem here is that port 3000 was never exposed, so when we attempt to ping the container, we aren’t pinging on a port on which the …

https://learn.microsoft.com/en-us/answers/questions/510881/azure-web-app-container-error?ref=cloudatlas

https://learn.microsoft.com/en-us/answers/questions/510881/azure-web-app-container-error?ref=cloudatlas
Azure Web App Container Error – Microsoft Q&A
Container for site did not start within expected time limit. Elapsed time = 250.9032383 sec Container didn’t respond to HTTP pings on port: 8080, failing site start. See container logs for debugging. Any help would be much appreciated. Thanks ThreeAtion Azure Container Instances Azure App Service Sign in to follow 0 comments Report a concern

https://serverfault.com/questions/1035064/why-does-a-restart-of-my-azure-webapps-instance-caused-downtime-of-a-few-hours

https://serverfault.com/questions/1035064/why-does-a-restart-of-my-azure-webapps-instance-caused-downtime-of-a-few-hours
tomcat – Why does a restart of my Azure WebApps instance caused …
If an instance does not respond within 10 minutes (5 pings), the instance is determined to be unhealthy and our service will stop routing requests to it. It is highly recommended for production apps to utilize this feature and minimize any potential downtime caused due to a faulty instance.

https://stackoverflow.com/questions/61169920/azure-web-app-for-container-failed-during-startup-didnt-respond-to-http-pin

https://stackoverflow.com/questions/61169920/azure-web-app-for-container-failed-during-startup-didnt-respond-to-http-pin
node.js – Azure web app for container – Stack Overflow
The details: azure web app for container with Linux OS on a Basic B1 machine. nodejs v12 LTS with express server listening on HTTPS port 443. Includes an HTTP 404 (Not Found) error handler. database db Mongodb Atlas on M0 Sandbox (free tier). Local and Azure IPs whitelisted. docker container using Dockerfile. no Kubernetes, no yml config file.

https://github.com/Azure/app-service-linux-docs/blob/master/Things_You_Should_Know/things_you_should_know.md

https://github.com/Azure/app-service-linux-docs/blob/master/Things_You_Should_Know/things_you_should_know.md
Things you should know: Web Apps on Linux – GitHub
However, at the end of the log, we see a message that the container did not start within the expected time limit. n. Notice in the next to the last line that the Node.js engine is listening on port 3000.

https://stackoverflow.com/questions/55688600/azure-web-app-on-linux-error-container-didnt-respond-to-http-pings-on-port

https://stackoverflow.com/questions/55688600/azure-web-app-on-linux-error-container-didnt-respond-to-http-pings-on-port
azure docker azure-devops azure-web-app-service – Stack Overflow
8 Answers Sorted by: 8 Are we trying to ping on PORT 8080? The problem here is that port 8080 is not exposed, so when we attempt to ping the container, we aren’t pinging on a port on which the container is listening. There are a couple of ways to resolve this. Use the EXPOSE instruction in your Dockerfile to expose port 8080.

https://github.com/MicrosoftDocs/azure-docs/issues/55944

https://github.com/MicrosoftDocs/azure-docs/issues/55944
Container xx_0_afc3de95 didn’t respond to HTTP pings on port: 8080 …
Elapsed time = 226.14369 sec 2020-05-29T05:38:15.145Z ERROR – Container upisite_0_99ae64d5 for site upisite did not start within expected time limit. Elapsed time = 235.0733223 sec 2020-05-29T05:38:15.154Z ERROR – Container upisite_0_99ae64d5 didn’t respond to HTTP pings on port: 8080, failing site . See container logs for debugging.

https://social.msdn.microsoft.com/Forums/en-US/e4a58aba-3123-48b5-a8ce-3c26bddb6ef2/app-service-suddenly-down-due-to-warmup-failing?forum=windowsazurewebsitespreview

https://social.msdn.microsoft.com/Forums/en-US/e4a58aba-3123-48b5-a8ce-3c26bddb6ef2/app-service-suddenly-down-due-to-warmup-failing?forum=windowsazurewebsitespreview
App Service suddenly down due to warmup failing
Elapsed time = 227.1849165 sec 2019-06-03 12:31:51.914 ERROR – Container zwiftly__51b2_0 for site zwiftly__51b2 did not start within expected time limit. Elapsed time = 230.2236921 sec And then it tries runs a docker run again which also fails and so it goes. According to the application logs, the application boots up fine every : lesoutrali bot