Journey of an App: How to Extract a Web App from IIS to Create a New Container Image
Published Aug 18 2020 12:01 AM 7,893 Views

Containers are becoming extremely popular these days and many ITPros are being asked to modernize existing applications and run those apps on Kubernetes. The process can be a bit challenging if you don't know how to get started, and more importantly if you don't have the right tools for the job.

In this video series we will go over the entire process of containerizing a web application running on Windows Server 2012 R2 on-premises to Azure with Azure Kubernetes Services. Here are some details on the tools used in this video, so you can try for yourself:

  • Sample web application: The process shown in the video can be performed in your application, but if you just want to test it, you can use this sample app as shown in the series.
  • Web Deploy: We'll be using it to export the application from IIS. Web Deploy makes the process of exporting an IIS web site way simpler than doing it manually. Plus, you can reconfigure some parameters like Database Connection in the process.
  • Windows Admin Center: The updated Containers extension now supports Web Deploy ZIP files as a source for new container images. With WAC you can point to a ZIP file from Web Deploy and WAC will do the hard work for you!

In this first video in the series, we cover how to extract the web application from IIS and use the exported ZIP file to create a new container image on Windows Admin Center. Check it out:
   

  

In the next video, we'll cover how to push this container image to Azure so you can reuse on other container hosts, or Azure services. The final video will cover how to prepare Azure Kubernetes Services to deploy this Windows Container hosting our exported application.

I hope you like the video and the series. Let us know what you think in the comments and what you'd like to see next!

 

Regards,

Vinicius.

Twitter: @vrapolinario

3 Comments
Iron Contributor

Dockerfile produced by Windows Admin center does not seem to be optimized. One shall delete all downloaded files as well as junk MSI leaves behind after installation in the SAME layer where installation took place. Microsoft has this recommendation spelled out as well in documentation

Thanks @Gregory Suvalian. You are correct. This feature was recently added and we missed adding the line to remove the MSI we used to install Web Deploy. I'll open a bug internally to add that to the functionality.

Aside from that, I hope you enjoy the functionality. Let us know if there's anything we can improve there.

Regards,

Vinicius.

Iron Contributor

Not only MSI itself needs to be removed but also installer files left behind in c:\windows\installer\* folder as well.

Version history
Last update:
‎Aug 18 2020 05:12 AM
Updated by: