As an undergraduate professor of computer science, I would love to have a how-to for Virtualization in Windows that made any sense.
Right now, the inability to use Docker containers in a simple reliable way that composes with the use of common virtualization (not hyper-v) in windows guarantees the students with windows laptops will have a poor experience with containers.
My ability to use containers in the classroom is blocked by this. The ability of Docker, the company, to have CS majors with a working and positive experience with containers is blocked by this as well.
This is not a small thing: I keep hoping to try containers to help fix compatibility issues across student dev environments, and instead I only find new ones. It is not reasonable for the “hello world” to be a glossy discussion, followed by a 10 page essay on choices and compatibility problems that is a mile deep for some sophomore who just wants their node app to run like everyone else’s.
Windows containers almost profoundly do not matter: nobody deploys them, they are almost always a bad idea, and nobody will consider teaching how to use them. Their introduction to the fray greatly harmed the original simplicity of the docker model: now there are red and blue ones. No-one uses the red ones, but they break everything and, oh, they are the only ones you can easily use in windows.
Docker, please, please, prioritizes a solution that supports your principle goals: simple compatible linux containers. For devs to enter the market with positive experiences, this means having that work in windows without hyper-V so they can use it in combination with other virtualization tools.
It ain’t a container if…
Gently ask docker to focus on their original killer app idea: maintainable, composable, lightweight linux containers.
I know! — Warren MacEvoy