@Deepika Balla , Apologies for the delayed response.
Typically, the error message ‘Container didnt respond to HTTP pings on port, failing site start
indicates that the application container did not send back an HTTP response to the platform ping in the predetermined time. Kindy try the following steps to isolate the issue and let us know how it goes.
- In most cases, the application should be listening on the same port that’s exposed by the container. If there is a mismatch here, the container will time out on startup. Review the
WEBSITES_PORT
app settings and /or or theEXPOSE
instruction in the Dockerfile - for right port to be enabled. - Review the binding to localhost : Applications should be listening on
0.0.0.0
instead. - By default, if your container does not respond after 230 seconds, it will time out. (This time out can be increased by with the
WEBSITES_CONTAINER_START_TIME_LIMIT
app setting.) (up to a maximum of 1800)
Ref: Troubleshooting ‘Container didnt respond to HTTP pings on port, failing site start’
If the issue persists,
4.To enable application logging for Linux apps or custom containers in the Azure portal, navigate to your app and select App Service logs.
Kindly let us know how it goes, I'll follow-up with you further.
If the answer helped (pointed, you in the right direction) > please click Accept Answer