Yesterday, we held a packed webinar on using the Image2Docker tool that prototypes shifting a legacy Windows virtual machine to a Windows Container Dockerfile.
Image2Docker is an open source, community generated powershell module that searches for common components of a Windows Server VM and generates a Dockerfile to match. Originally created by Docker Captain Trevor Sullivan, it is now an open source tool hosted in our GitHub repository. Currently there is discovery of components such IIS, Apache, SQL Server and more. As an input it supports VHD, VHDX, and WIM files. When paired with Microsoft’s Virtual Machine Converter, you can start with pretty much any VM format.
Image2Docker is community supported and designed to show you how easy it is to create Windows Containers from your existing servers. We strongly encourage you to fork it, play with it and contribute pull requests back to the community. Or just install it and use it to generate your own Dockerfiles.
Watch the on-demand webinar to learn more about how it was built, how to use it, and how to contribute.
Is it possible to containerize an application based on older versions of Windows Server?
Anything you can run on Windows 2016, you can run in Docker, with the exception of anything that requires a GUI. That includes .NET applications, SQL Server, IIS, and all the Windows Server components.
Are there any success stories of people building applications using Docker for Windows Server?
Yes. Tyco has been working with Docker and Windows Server 2016 since Tech Preview and their story is featured here.
Can I run the Windows Server image as a container on a Linux host or any other OS?
For licensing reasons, Windows Server images will currently run on Windows Server 2016 and Windows 10 only.