Windows Container in Azure and Network

Question

Windows Container in Azure and Network

Hi,

I have an old legacy application listening to some tcp ports and written in visual c++ and strictly bound to run on windows.

On Prem the application is running fine within a windows server core container. But now I have to deploy this container to azure. Azure in turn does not support windows container to connect to a vnet. Why? Where is the limitation? Are there any work arounds to run windows containers (server core) within a vnet in azure?

Thanks in advance

prmanhas-MSFT 17,541 Reputation points Microsoft Employee

2020-12-08T12:12:34.86+00:00

@Torsten Mattetat Apologies for the delay in response and all the inconvenience caused because of the issue.
I have reached out to our internal team on the issue and once I have an update will keep you posted on same.

Thank you for your patience over the matter.

Thanks.
Torsten Mattetat 26 Reputation points

2020-12-08T14:32:44.66+00:00

Thx, I also opened a feature request: https://feedback.azure.com/forums/602224-azure-container-instances/suggestions/42151789-windows-conteiner-vnet
I dont want and due to policies I am not allowed to use a public ip since the service is internal only. And our goal is PaaS not IaaS, so a new vm hosting the containers is not an option.
prmanhas-MSFT 17,541 Reputation points Microsoft Employee

2020-12-15T15:50:46.883+00:00

@Torsten Mattetat Firstly, apologies for the delay in responding on this and any inconvenience this issue may have caused.
Can you please confirm if this is a Windows 2016 or Windows 2019 container? ACI has been investing in infrastructure improvements that will enable Vnet deployments for Windows 2019 (after 3b) images early 2021.

Thanks
Anonymous

2020-12-15T22:19:00.553+00:00

Many thanks, That are great news.
Yes, I want to deploy a Windows Server Core 2019.
Is there any roadmap or something similar I can see? When is the approximative release date for this feature?

prmanhas-MSFT 17,541 Reputation points Microsoft Employee

2020-12-08T12:12:34.86+00:00

@Torsten Mattetat Apologies for the delay in response and all the inconvenience caused because of the issue.
I have reached out to our internal team on the issue and once I have an update will keep you posted on same.

Thank you for your patience over the matter.

Thanks.
Torsten Mattetat 26 Reputation points

2020-12-08T14:32:44.66+00:00

Thx, I also opened a feature request: https://feedback.azure.com/forums/602224-azure-container-instances/suggestions/42151789-windows-conteiner-vnet
I dont want and due to policies I am not allowed to use a public ip since the service is internal only. And our goal is PaaS not IaaS, so a new vm hosting the containers is not an option.
prmanhas-MSFT 17,541 Reputation points Microsoft Employee

2020-12-15T15:50:46.883+00:00

@Torsten Mattetat Firstly, apologies for the delay in responding on this and any inconvenience this issue may have caused.
Can you please confirm if this is a Windows 2016 or Windows 2019 container? ACI has been investing in infrastructure improvements that will enable Vnet deployments for Windows 2019 (after 3b) images early 2021.

Thanks
Anonymous

2020-12-15T22:19:00.553+00:00

Many thanks, That are great news.
Yes, I want to deploy a Windows Server Core 2019.
Is there any roadmap or something similar I can see? When is the approximative release date for this feature?

Answer 1

prmanhas-MSFT 17,541 Microsoft Employee

@Torsten Mattetat Posting as answer for broader community.

ACI has been investing in infrastructure improvements that will enable Vnet deployments for Windows 2019 (after 3b) images early 2021.

As per confirmation from our backend team there is a work item for same and is being worked upon as well.We don't have any ETA as such for now but it is for sure in pipeline and is being taken care of by Product Group.

Hope it helps!!!

Please "Accept as Answer" if it helped so it can help others in community looking for similar topics.

Gleb Smolnik 6 Reputation points

2021-06-07T21:12:54.677+00:00

Hey @prmanhas-MSFT , are there any updates on this matter? We are already in mid-2021 :) but I did not find any news on private or public preview of this feature. Is there any chance to get the latest status for it?
Thanks!
Torsten Mattetat 26 Reputation points

2021-06-08T05:43:29.253+00:00

I just moved to AKS an it works fine.
Gleb Smolnik 6 Reputation points

2021-06-08T12:04:49.54+00:00

I reviewed several options for running containers in Azure, and ACI seems to be the simplest for our case since we do not need any orchestration for example. But without VNet we will probably move to other services.
Torsten Mattetat 26 Reputation points

2021-06-08T18:32:15.79+00:00

We also do not need any orchestration for our windows containers. We simply had a small kubernetes deployment yaml to deploy the containers as Service with one replica. AKS also fixed some other inconvenient situations like executing command shells or unexpected container shutdowns. With ACI we had sometimes issues connecting to the container by the azure portal. Switching to AKS solved any issues by now.
DIT Terminal 1 Reputation point

2022-08-16T14:34:46.157+00:00

Hi, are there any updates concerning this? We're already in 2022 and private networking for windows containers is still not available

Answer 2

You can run Windows Containers on Azure App Service which has all the PaaS features that you need without the complexity of managing a cluster.

Please checkout our quickstart:
https://learn.microsoft.com/en-us/azure/app-service/quickstart-custom-container?tabs=dotnet&pivots=container-windows

You just simply need to join the containers to your VNet. For more info:
https://learn.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet

Windows Container in Azure and Network

1 additional answer

Activity