Run a custom Windows container in Azure (Preview)
Azure App Service provides pre-defined application stacks on Windows like ASP.NET or Node.js, running on IIS. The preconfigured Windows environment locks down the operating system from administrative access, software installations, changes to the global assembly cache, and so on (see Operating system functionality on Azure App Service). If your application requires more access than the preconfigured environment allows, you can deploy a custom Windows container instead. This quickstart shows how to deploy a custom IIS image to Azure App Service from Docker Hub.
Sign in to Azure
Sign in to the Azure portal at https://portal.azure.com.
Create a Windows container app
Choose Create a resource in the upper left-hand corner of the Azure portal.
In the search box above the list of Azure Marketplace resources, search for and select Web App for Containers.
Provide an app name, such as mywebapp, accept the defaults to create a new resource group, and click Windows (Preview) in the OS box.
Create an App Service plan by clicking App Service plan/Location > Create new. Give the new plan a name, accept the defaults, and click OK.
Click Configure container, type microsoft/iis:latest in Image and optional tag, and click OK.
In this article, you use the public microsoft/iis:latest Docker Hub image. If you have a custom image elsewhere for your web application, such as in Azure Container Registry or in any other private repository, you can configure it here.
Click Create and wait for Azure to create the required resources.
Browse to the container app
When the Azure operation is complete, a notification box is displayed.
Click Go to resource.
In the app page, click the link under URL.
A new browser page is opened to the following page:
Wait a few minutes and try again, until you get the IIS welcome page:
Congratulations! You're running your first custom Windows container in Azure App Service.
See container start-up logs
It may take some time for the Windows container to load. To see the progress, navigate to the following URL by replacing <app_name> with the name of your app.
The streamed logs looks like this:
2018-07-27T12:03:11 Welcome, you are now connected to log-streaming service. 27/07/2018 12:04:10.978 INFO - Site: win-container-demo - Start container succeeded. Container: facbf6cb214de86e58557a6d073396f640bbe2fdec88f8368695c8d1331fc94b 27/07/2018 12:04:16.767 INFO - Site: win-container-demo - Container start complete 27/07/2018 12:05:05.017 INFO - Site: win-container-demo - Container start complete 27/07/2018 12:05:05.020 INFO - Site: win-container-demo - Container started successfully
Use a different Docker image
You are free to use a different custom Docker image to run your app. However, you must choose the right parent image for the framework you want:
- To deploy .NET Framework apps, use a parent image based on the Windows Server Core 2016 Long-Term Servicing Channel (LTSC) release.
- To deploy .NET Core apps, use a parent image based on the Windows Server Nano 2016 Long-Term Servicing Channel (LTSC) release.
It takes some time to download a parent image during app start-up. However, you can reduce start-up time by using one of the following parent images that are already cached in Azure App Service: