Docker Compose - keep showing info - 'Stopping site xxx because it failed during startup"

it prizm 6

When use Docker Compose to build a container or multi-containers in Azure Web app, never download requested images and bring up instances, even restart App services.

repeat log:

2021-06-03T08:08:29.099Z INFO - Stopping site xxx-app because it failed during startup.
2021-06-03T08:12:44.289Z INFO - Stopping site xxx-app because it failed during startup.
2021-06-03T08:17:24.883Z INFO - Stopping site xxx-app because it failed during startup.
2021-06-03T08:22:06.149Z INFO - Stopping site xxx-app because it failed during startup.
2021-06-03T08:26:20.020Z INFO - Stopping site xxx-app because it failed during startup.
2021-06-03T08:31:10.644Z INFO - Stopping site xxx-app because it failed during startup.

1 answer

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-04T16:07:05.68+00:00

@it prizm , Thanks for posting the question.

There could be many causes for this start-up errors. To isolate, kindly find more error details in the docker logs:

1.You may also review the logs Azure Portal and also logs at Kudu- https://<yourwebpp-name>.scm.azurewebsites.net/api/logs/docker

2.Only supports to expose the port 80 and 443.

By default, App Service assumes your custom container is listening on port 80.
If your container listens to a different port, set the WEBSITES_PORT app setting in your App Service app.
App Service currently allows your container to expose only one port for HTTP requests.

In the Docker log, see if ‘docker run’ command was run, Review to see if ports are exposed.

Please see this doc:
https://learn.microsoft.com/azure/app-service/faq-app-service-linux#multi-container-with-docker-compose
Please sign in to rate this answer.
ajkuma 26,216 Reputation points Microsoft Employee

2021-06-04T16:16:42.24+00:00

@it prizm , Adding more info:

When we start your container, we'll wait a while for it to start and initialize.
We consider the startup to be successful once the container is running and once we get a response to a ping so that we know it's ready to respond to HTTP traffic.
We'll wait 230 seconds for that to happen. If we don't have a successful start within 230 seconds, we'll assume there's a problem and we'll stop the container.

If you container takes a long time, you could add an app setting:

WEBSITES_CONTAINER_START_TIME_LIMIT to 1800 (sec)

To do this, from the Azure Portal> Navigate to your WebApp > Under Settings blade > Go to Configuration > Add the above app setting with ‘Name’ with 1800 as ‘Value’ .

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-04T16:17:39.437+00:00

@it prizm ,

Also, please checkout this doc for Docker Compose options (support and unsupported) options:
https://learn.microsoft.com/azure/app-service/configure-custom-container?pivots=container-linux#configure-multi-container-apps

Kindly let us know how it goes, I'll follow-up with you further.

Also, share more information about your application framework and the App Service Plan (ASP) you’re leveraging (you may consider, scaling-up the ASP to test).

it prizm 6 Reputation points

2021-06-09T05:00:05.373+00:00

Thank you for the reply

We done all these app setting before and still no response in docker-compose for new deployment.
"you mention that If we don't have a successful start within 230 seconds, we'll assume there's a problem and we'll stop the container"
I think that our Web App service unable to stop current container and keep stopping ( or no response)
Is that any solution to force clear the old/existing container ?

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-09T19:22:42.21+00:00

@it prizm , Thanks for the follow-up.

Your container must respond to an HTTP ping. So for the wait time, in order for App Service to consider a container to be successfully started, the container must start and it must respond to an HTTP ping.
If the container starts but does not respond to a ping, App Service eventually log an event in the Docker log saying that it didn't start.

Something similar to - "ERROR - Container for site yourwebname did not start within expected time limit. Elapsed time = 230.0443067 sec".

So, kindly let us know of there any specific errors in the docker logs.
Kudu- https://<yourwebpp-name>.scm.azurewebsites.net/api/logs/docker

When you use a multi-container deployment with either Docker Compose, all containers specified in your configuration file must start successfully in order for the deployment to succeed. If one of your containers fails to start, all of them will fail.

ajkuma 26,216 Reputation points Microsoft Employee

2021-06-09T19:24:13.32+00:00

Additionally,
For the image pull, if your multi-container (Docker Compose) app uses more than one private image, make sure the private images are in the same private registry and accessible with the same user credentials.

Just to highlight on container start-up process - When your site starts, we run your Docker image and create a Docker container. Your app runs inside of that container, and the file system contains only what is in the Docker image. If your Docker image doesn't install a particular component, it won't be there when your container starts. You can provide an optional startup command that will be run as part of container startup. From “Startup Command” under WebApp “General settings”.

To isolate the issue we would more details on your application framework, docker logs and WebApp details. Kindly let us know how the above goes, I’ll follow-up with you privately.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Docker Compose - keep showing info - 'Stopping site xxx because it failed during startup"

1 answer

Your answer