In fact, most of the solution requires low resource for handling one request at a time. This is the red-arrow roundtrip in the diagram and its impact performances.Īs Docker on Windows for running Linux container if used mostly in a development environment, performance doesn't matter a lot. The container image is inside the VM, it stores files in volumes, but you may want to share folders from the Windows environment, especially when developing. This lead to the same performance issues we had using virtual machines. While docker is designed for sharing OS, a hypervisor still use hardware, and you need to allocate resources to it.

The big problems with this architecture are: How docker development works in “Linux over Windows” mode. That’s how things work, and I tried to explain it using a diagram. Docker Desktop for windows use a Hypervisor (usually Microsoft HyperV) for running a virtual machine, and it shares the VM OS to the docker container. We cannot have a Linux container on Windows, but we can put Linux in windows machine by using a hypervisor. But everybody uses Linux containers on windows, how it is possible? Docker engineers solved this problem with a trick. Because it shares the OS, not the hardware, you couldn’t have any Linux based containers on Windows. The central part to remark about Docker is how it works under windows. Anyway, if you want to know more about docker, you can read this article where I tried to explain in simple words“ what is exactly docker”.

If you are here, probably already use it, so I will spend just a few words for introducing the limitation that WSL2 overcome. I don't want to spend a lot of time talking about what docker is. Photo by CHUTTERSNAP on Unsplash How WSL2 change Docker How docker worksĭocker is the leading container solution, active since 2013.

Docker on mac performance