Container didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.

Question

I have deployed an App Service via Github Workers with node.js now i have the problem, that the node.js Application is running, but the Ports is not exposing. Can everyone give me an advice or is it possible to deactivate HTTP pings? Logs: 2020-11-19T16:19:27.439Z INFO - Initiating warmup request to container X for site X 2020-11-19T16:19:43.733Z INFO - Waiting for response to warmup request for container X. Elapsed time = 16.2938836 sec 2020-11-19T16:23:27.969Z ERROR - Container Xf for site X did not start within expected time limit. Elapsed time = 240.5298169 sec 2020-11-19T16:23:27.970Z ERROR - Container X didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging. 2020-11-19T16:23:27.980Z INFO - Stopping site X because it failed during startup. Kind regards, Noah

Answer 1

I am facing the same problem, saying my node js port 3000 can not be ping so the container exit even I have done following

Use the EXPOSE instruction in your Dockerfile to expose port 3000.
Use the WEBSITES_PORT app setting with a value of "3000" to expose that port.

have seen many other posts out there suggesting same solution, but setting WEBSITES_PORT does not work. My image works perfectly locally..

2021-08-14T23:01:18.250Z INFO - Logging is not enabled for this container.
Please use https://aka.ms/linux-diagnostics to enable logging to see container logs here.
2021-08-14T23:01:20.821Z INFO - Initiating warmup request to container xxxx for site xxxx
2021-08-14T23:01:20.832Z INFO - Container xxxxx for site xxxx initialized successfully and is ready to serve requests.
2021-08-14T23:01:20.832Z INFO - Initiating warmup request to container xxx for site xxx
2021-08-14T23:01:21.875Z ERROR - Container xxx for site xxx has exited, failing site start
2021-08-14T23:01:21.877Z ERROR - Container xxx didn't respond to HTTP pings on port: 3000, failing site start. See container logs for debugging.
2021-08-14T23:01:21.889Z INFO - Stopping site xxx because it failed during startup.

Answer 2

We have the same issue. The container suddenly fails to restart after being online for a while and then never starts.

Have tried to set the WEBSITES_PORT (and/or) PORT to 8080 and we are exposing 8080 in our Dockerfile.

The image works perfectly locally.

Answer 3

We had the above error message for a docker container and as well standard_init_linux.go:228: exec user process caused: exec format error

We have resolved it by specifying the architecture (platform) when building the app with docker (required when you running docker e.g. on a Mac).

See this comment: https://github.com/Azure/azure-sdk-for-js/issues/21572#issuecomment-1111869403 and follow this tutorial https://learn.microsoft.com/en-us/azure/developer/javascript/tutorial/tutorial-vscode-docker-node/tutorial-vscode-docker-node-04

Answer 4

Any known solution for this problem?

Tried below things

1. Restarted -- multiple times
2. Set below mentioned Env variables as well

App Details
Node js Application

Docker is exposing 8080 port
App running on 8080 port

gave PORT as env variable which is set to 8080 - used in App to run the server

set WEBSITES_PORT to 8080

gave high number for WEBSITES_CONTAINER_START_TIME_LIMIT

Stopped and started the container multiple times

Answer 5

Thanks for your Answer. The Application is responding in a SSH Session with a HTTP 200 OK (curl 127.0.0.1:8080). But from external the App isn't responding. Can you give me any advice on other Plattforms i don't find any answer thats seems to work. The node.js Application is binded on 0.0.0.0