Azure App Service using a Windows container Failing and restarting - Modify Compute System failed

Brandon Joseph 1 Reputation point
2020-02-06T00:26:05.707+00:00

I have a docker built container which 1) runs in linux/ windows desktop which will run in azure when used as a web app in azure.

I built it again on a windows 2016 server running docker and it works locally on that machine.

When I try to run it as an Azure web app it stops and starts with no logs apart from:

06/02/2020 00:16:07.981 INFO - Site: fontapp-ltsc2016 - Pulling container image: customfontsample20200205051659.azurecr.io/customfontsample:latest
06/02/2020 00:16:07.981 INFO - Site: fontapp-ltsc2016 - Pulling from custom registry: https://customfontsample20200205051659.azurecr.io
06/02/2020 00:16:07.981 INFO - Site: fontapp-ltsc2016 - Pulling image using registry credentials
06/02/2020 00:16:08.039 INFO - Site: fontapp-ltsc2016 - Image: customfontsample20200205051659.azurecr.io/customfontsample:latest
Custom Registry: https://customfontsample20200205051659.azurecr.io
Status: latest Pulling from customfontsample

06/02/2020 00:16:08.042 INFO - Site: fontapp-ltsc2016 - Image: customfontsample20200205051659.azurecr.io/customfontsample:latest
Custom Registry: https://customfontsample20200205051659.azurecr.io
Status: Digest: sha256:2ae54737a5f055051f549852463aad006d396888fcda9afaf9279364a41712bd

06/02/2020 00:16:08.042 INFO - Site: fontapp-ltsc2016 - Image: customfontsample20200205051659.azurecr.io/customfontsample:latest
Custom Registry: https://customfontsample20200205051659.azurecr.io
Status: Status: Image is up to date for customfontsample20200205051659.azurecr.io/customfontsample:latest

06/02/2020 00:16:08.088 INFO - Site: fontapp-ltsc2016 - Creating container for image: customfontsample20200205051659.azurecr.io/customfontsample:latest.
06/02/2020 00:16:08.132 INFO - Site: fontapp-ltsc2016 - Create container for image: customfontsample20200205051659.azurecr.io/customfontsample:latest succeeded. Container Id 44b53a0d14fc7dc155fda02519461a18e46b06706576e80b5820111b4a388417
06/02/2020 00:16:09.089 INFO - Site: fontapp-ltsc2016 - Application Logging (Filesystem): On
06/02/2020 00:16:28.960 INFO - Site: fontapp-ltsc2016 - Application Logging (Filesystem): On
06/02/2020 00:16:47.637 INFO - Site: fontapp-ltsc2016 - Start container succeeded. Container: 44b53a0d14fc7dc155fda02519461a18e46b06706576e80b5820111b4a388417
06/02/2020 00:16:50.665 INFO - Site: fontapp-ltsc2016 - Attempting to stop container: 44b53a0d14fc7dc155fda02519461a18e46b06706576e80b5820111b4a388417
06/02/2020 00:16:51.393 INFO - Site: fontapp-ltsc2016 - Container stopped successfully. Container Id: 44b53a0d14fc7dc155fda02519461a18e46b06706576e80b5820111b4a388417
06/02/2020 00:16:51.393 INFO - Site: fontapp-ltsc2016 - Purging pending logs after stopping container
06/02/2020 00:16:51.420 ERROR - Site: fontapp-ltsc2016 - Unable to start container. Error message: Modify Compute System failed.
06/02/2020 00:16:51.420 INFO - Site: fontapp-ltsc2016 - Purging after container failed to start
06/02/2020 00:18:21.296 INFO - Site: fontapp-ltsc2016 - Cancelling pending tasks.

Can anyone help?

The base images I tried was:

FROM mcr.microsoft.com/dotnet/framework/aspnet:4.7.2-windowsservercore-ltsc2016

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,913 questions
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. brtrach 251 Reputation points
    2020-02-07T03:03:42.76+00:00

    Windows Containers an App Service that use Windows Server 2016 base images (for example microsoft/aspnet:4.7-windowsservercore-ltsc2016) to fail to start. This issue is the result of a recent platform upgrade intended to introduce improvements on networking capabilities. We are working with other teams at Microsoft responsible for networking components to further understand this current limitation.

    Since your base image is 2016, can you please use the Windows Server 2019 base image (for example: microsoft/aspnet:4.7.2-windowsservercore-ltsc2019). An added benefit of this change will be faster load times and higher cost effectiveness due to significantly smaller image size. Please check this announcement for more info on this: https://azure.microsoft.com/en-us/updates/windows-server-2019-support-added-to-public-preview-of-windows-container-support/ .

    Please refer to the Docker Hub repo for windows server 2019 based aspnet images: https://hub.docker.com/_/microsoft-dotnet-framework-aspnet

    0 comments
  2. saathvik Jadhav 1 Reputation point
    2021-02-19T03:27:28.863+00:00

    Is this resolved yet? I tried to deploy a docker container using aspnet:4.7-windowsservercore-ltsc2016 and it is failing to start.

    0 comments
  3. Ankit Gupta 1 Reputation point
    2021-06-01T04:09:45.673+00:00

    I a still facing the same issue with Windows server 2016

    0 comments
  4. Phil Boyd 1 Reputation point
    2021-08-09T23:22:35.723+00:00

    I'm getting a similar issue using the 2019LTSC image

    0 comments