Issue link: https://insights.oneneck.com/i/1293607
CHAPTER 4 Preparing for and Testing Docker Containers 33 These materials are © 2017 John Wiley & Sons, Inc. Any dissemination, distribution, or unauthorized use is strictly prohibited. That said, unlike the older methodology, the latest Docker for Windows can be used for production workloads, so it's far and away better than what came before. Containerized Workload Deployment Options As was the case with virtualization, containerization projects ulti- mately take one of three forms: » Greenfield: You start from scratch and don't bring over anything from the legacy environment. » Full migration: You have to migrate all your legacy work- loads from the old environment into the container environment. » Hybrid: You have some new applications and some legacy applications and need to develop a strategy for deploying both. As you might imagine, the hybrid scenario is the most com- mon deployment method for pretty much any new kind of infrastructure. Migrating Windows-based web applications from virtual machines Deploying new workloads is pretty obvious, but a whole lot of people will need to migrate legacy applications to containers if they're interested in going all-in on the technology. A LINUX WORKAROUND FOR WINDOWS If you've got a lot invested in your Linux-based Docker environment, but need to move to Windows anyway, you can still choose to run those Linux containers under a Linux virtual machine in Hyper-V rather than using the native Docker for Windows tools.