Image2Docker Introduction
Docker
Image2Docker is a PowerShell module which ports existing Windows application workloads to Docker. It supports multiple application types, but the initial focus is on IIS and ASP.NET apps. You can use Image2Docker to extract ASP.NET websites from a VM - or from the local machine or a remote machine. Then so you can run your existing apps in Docker containers on Windows, with no application changes.
Image2Docker also supports Windows Server 2012, with support for 2008 and 2003 on its way. The websites on this VM are a mixture of technologies – ASP.NET WebForms, ASP.NET MVC, ASP.NET WebApi, together with a static HTML website.
To learn more about Image2Docker, please visit the following link
https://github.com/docker/communitytools-image2docker-win
Microsoft Windows 10 and Windows Server 2016 introduced new capabilities for containerizing applications.There are two types of container formats supported on the Microsoft Windows platform:
- Hyper-V Containers - Containers with a dedicated kernel and stronger isolation from other containers
- Windows Server Containers - application isolation using process and namespace isolation, and a shared kernel with the container host
Prerequisite
- PowerShell 5.0 needs to be installed to use Image2Docker.
Download URL: https://www.microsoft.com/en-us/download/details.aspx?id=50395
- Image2Docker generates a Dockerfile which you can build into a Docker image. The system running the ConvertTo-Dockerfile command does not need Docker installed, but you will need Docker setup on Windows to build images and run containers.
Installation
- Open PowerShell with administrative privileges. Run the following commands
Install-Module Image2Docker Import-Module Image2Docker - You can validate the presence of the Install-Module command by running: Get-Command -Module PowerShellGet -Name Install-Module. If the PowerShellGet module or the Install-Module commands are not accessible, you may not be running a supported version of PowerShell. Make sure that you are running PowerShell 5.0 or later on a given machine.
Usage
- Image2Docker can inspect web servers and extract a Dockerfile containing some or all of the websites configured on the server. ASP.NET is supported, and the generated Dockerfile will be correctly set up to run .NET 2.0, 3.5 or 4.x sites.
- Image2Docker Supports the following source types.
- Local Machines
- Remote Path
- Disk Images
The following commands show how to setup and run Image2Docker on local machines. Instructions on how to run it on remote path and disk images will be covered in future blog posts.
Local Machines
- This mode looking for the IIS installed on the local machine and convert the IIS sites /virtual directories/ applications to docker files associate artifacts.
- Run the following command
ConvertTo-Dockerfile ` -Local ` -OutputPath {{OutputPath}} ` -Artifact IIS ` -Verbose - Local parameter used for iis discovery on local machines.
- OutputPath parameter specifying the location to store the generated Dockerfile and associated artifacts.
- Artifact parameter specifies what artifact to inspect. In our case this is IIS.
- Verbose parameter is optional and it will give all the verbose logs.
- Following is the sample command
ConvertTo-Dockerfile -Local -OutputPath c:\docker_repo\iis -Artifact IIS -Verbose
Share this:
Take a look at the lastest aricles
Part 4 of our series on intent-driven development. Start with Part 1, or read Parts 2 and 3 first if you want the technical workflow before the outcomes. The first three posts in this series covered the mechanics: why the spec is now the source of truth, how to build the CLAUDE.md context layer, and how OpenSpec moves […]
Part 3 of our series on intent-driven development. Read Part 1 (spec-driven development with Kiro) and Part 2 (mastering the CLAUDE.md file) first. Part 1 of this series established the principle: in AI-assisted development, the spec is the source of truth, not the code. Part 2 covered the CLAUDE.md file — the context layer that ensures every AI session starts from […]
How to Master the CLAUDE.md File: The Context Layer That Makes Spec-Driven Development Work Part 2 of our series on intent-driven development. If you haven't read Part 1 — Code is No Longer the Source of Truth. Your Spec Is. — start there. In Part 1, we explored how spec-driven development with tools like Kiro shifts the source of truth from […]
Let’s shape your AI-powered future together.
Partner with CloudIQ to achieve immediate gains while building a strong foundation for long-term, transformative success.