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

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 2

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 3

I saw this problem as well, and the issue turned out to be me building images locally on my Mac M1. In App Service, containers are likely using the x64 architecture instead of ARM. I fixed the issue by forcing docker to build for linux-amd64 (--platform linux-amd64) when pushing to my remote registry. After that, I was able to start up fine.

That being said, the UX could be better here. It's fairly trivial to get the architecture of an image in a registry. App Service could alert you that it was built using the incorrect architecture for a better debugging experience.

Hope this helps others!

Answer 4

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

Answer 5

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.