A few days ago, I showed you how to deploy Windows Containers to Microsoft Azure using App Service and today I will show you how to connect a running Windows Container in Azure.
About windows Containers in Azure App Service
Windows Containers in Azure App Service allows you to deploy windows Containers using any Container registry including Docker hub, Azure Container registry or private registry.
To read more about the deployment process please visit this article
Get Started
To enable Win-RM on a Windows Container in Azure from the Web APP where to Windows Container was deployed click on win-RM
From the Win-RM screen click On to enable Win-RM and copy the connection script
Using Powershell ISE I will paste the code to and save it or use ISE to run it
After saving the code, I will click run and confirm that I would like to add my machine to the Trustedhosts list.
After connecting I can run any Windows PowerShell cmdlet on my Windows Container
About Windows Containers in Azure
The new service brings Windows Containers to Microsoft Azure like AKS by simplifying the deployment of containers without installing a Container a host as a Virtual Machine.
With the public release the Windows Containers Images are supported
- microsoft/iis:windowsservercore-ltsc2016, latest
- microsoft/iis:nanoserver-sac2016
- microsoft/aspnet:4.7.2-windowsservercore-ltsc2016, 4.7.2, latest
- microsoft/dotnet:2.1-aspnetcore-runtime
- microsoft/dotnet:2.1-sdk
Features
Deploy images directory from Docker Hub, Azure Container Registry or private registry.
- Web apps can be scaled easily using auto-scale
- Win-Rm access to containers (disabled by default)
- Allow SSL only and add custom domain \ Certificate
How do you remotely access multiple containers in your app service? The option you have chosen will only connect to one of the containers. What if you have scaled out to 2 containers? How do you access the second container?