Hi Team I have a issue about topic:
https://github.com/Azure/app-service-linux-docs/blob/master/Things_You_Should_Know/things_you_should_know.md#if-your-container-takes-a-long-time-to-start-increase-the-start-time-limit
1-st I didnt have a fails in the default_docker.logs only:
2025-01-13T12:32:41.799Z INFO - Initiating warmup request to container XXX
2025-01-13T12:32:56.863Z INFO - Waiting for response to warmup request for container XXX. Elapsed time = 15.0638285 sec
2025-01-13T12:32:57.873Z ERROR - Container XXX for site XXX has exited, failing site start
What configuration do these 15 seconds come from and why 15 seconds?
This is answer from MST support team:
The WEBSITES_CONTAINER_START_TIME_LIMIT app setting increases the maximum time allowed for a container to start before timing out. The default is 230 seconds. This setting applies to both custom containers and blessed images. Although the attached screenshot from the trial email pertains to custom containers, it is also relevant for blessed images.
Elapsed Time refers to the time taken for a specific task, which in this case is the container boot-up time. By default, the platform waits for 230 seconds for the container to boot up, provided there are no application errors during the boot process.
If the application encounters errors, the boot-up process fails. You should check the default_docker.logs for any application-related errors during boot-up. Correlate the time frame of the errors with the boot-up attempt to diagnose the issue.
Question is this mistake in the documentation ? or this parameter not applicable for .NET ?
https://github.com/Azure/app-service-linux-docs/blob/master/Things_You_Should_Know/things_you_should_know.md#if-your-container-takes-a-long-time-to-start-increase-the-start-time-limit
-
For CODE scenarios, App Service provides a base container that is maintained by the platform. This container targets a specific development framework (.NET Core, PHP, Node, etc...) and a specific version of that framework (.NET Core 3.0, .NET Core 3.1, etc...).
-
For CONTAINER scenarios, App Service provides a host where a custom container provided by the customer can execute.
Thank you.
Hi Team I have a issue about topic:
https://github.com/Azure/app-service-linux-docs/blob/master/Things_You_Should_Know/things_you_should_know.md#if-your-container-takes-a-long-time-to-start-increase-the-start-time-limit
1-st I didnt have a fails in the default_docker.logs only:
2025-01-13T12:32:41.799Z INFO - Initiating warmup request to container XXX
2025-01-13T12:32:56.863Z INFO - Waiting for response to warmup request for container XXX. Elapsed time = 15.0638285 sec
2025-01-13T12:32:57.873Z ERROR - Container XXX for site XXX has exited, failing site start
What configuration do these 15 seconds come from and why 15 seconds?
This is answer from MST support team:
The WEBSITES_CONTAINER_START_TIME_LIMIT app setting increases the maximum time allowed for a container to start before timing out. The default is 230 seconds. This setting applies to both custom containers and blessed images. Although the attached screenshot from the trial email pertains to custom containers, it is also relevant for blessed images.
Elapsed Time refers to the time taken for a specific task, which in this case is the container boot-up time. By default, the platform waits for 230 seconds for the container to boot up, provided there are no application errors during the boot process.
If the application encounters errors, the boot-up process fails. You should check the default_docker.logs for any application-related errors during boot-up. Correlate the time frame of the errors with the boot-up attempt to diagnose the issue.
Question is this mistake in the documentation ? or this parameter not applicable for .NET ?
https://github.com/Azure/app-service-linux-docs/blob/master/Things_You_Should_Know/things_you_should_know.md#if-your-container-takes-a-long-time-to-start-increase-the-start-time-limit
For CODE scenarios, App Service provides a base container that is maintained by the platform. This container targets a specific development framework (.NET Core, PHP, Node, etc...) and a specific version of that framework (.NET Core 3.0, .NET Core 3.1, etc...).
For CONTAINER scenarios, App Service provides a host where a custom container provided by the customer can execute.
Thank you.