When a developer wants to have more control over what is installed in their containers, now can use Windows Server Containers in Web App. The public preview has released to community.
Now it supports Windows Containers on Azure App Service and enables number of opportunities for Application
- Relaxed security restrictions – The Windows Container is an isolation and security boundary, When deploying a containerized application. Normally Libraries will be blocked by Azure App Service and instead of it will be succeed when running inside of a Windows Container
- Lift and Shift to PaaS – When a developer wants to migrate .NET Framework and .NET Core applications to Azure, and is trying to transform straight to a PaaS service to get the many productivity benefits from the App Service platform.
- Third-party application migration – Customers often have business critical applications developed by third parties with which the company no longer has a relationship. Containerizing these types of applications unlocks the opportunity to migrate applications to Azure App Service.
- Applications with dependencies – Ina scenario, when a developer deploying an app within a Windows Container, it allows to install custom dependencies. Even when a developer wants to install libraries into Global Assembly Cache (GAC) done by easily.
With the release of Windows Container support, Microsoft also adding three new premium SKUs exclusively for App Service Plans hosting applications deployed using Windows Containers. These new SKUs all provide Dv3 series capabilities, offering customers more choice for their applications. The new Premium Container Tier offers customers three options in which to run their containers:
- Small (2 CPU vcores, 8GB Memory)
- Medium (4 CPU vcores, 16GB Memory)
- Large (8 CPU vcores, 32GB Memory)
Microsoft Initially offer a free preview for these new SKUs during the month of August. Preview pricing will take affect starting September 13, 2018.
Currently just like every container Windows Containers deployed on Azure App Service are also derive from a base Windows image. For the easiness Microsoft has cached several base images on their infrastructure and developers and users to advice to use those images as the base of their containers to enable faster application startup times. Customers are also free to use their own base images, though using different base images will lead to longer application startup times.
Customers deploying .NET Framework Applications must choose a base image based on the Windows Server Core 2016 Long Term Servicing Channel release. Customers deploying .NET Core Applications must choose a base image based on the Windows Server Nano 2016 Long Term Servicing Channel release. At this point, Azure App Service does not support deployment of applications in containers based on the Windows Server 1709 release.
Cached base images:
- microsoft/iis:windowsservercore-ltsc2016, latest
- microsoft/aspnet:4.7.2-windowsservercore-ltsc2016, 4.7.2, latest
Capabilities of Public preview
- Deploy containerized applications using Docker Hub, Azure Container Registry, or private registries.
- Incrementally deploy apps into production with deployment slots and slot swaps.
- Scale out automatically with auto-scale.
- Enable application logs and use the App Service Log Streaming feature to see logs from your application.
- Use PowerShell and Win-RM to remotely connect directly into your containers.