Process Vs Hyper V Isolation Modes

Isolation is provided on a per-container level by the Docker Engine.
Using containers, multiple applications can be deployed to a single bare metal
server without any conflict between the applications.

Windows containers on Docker can run in two distinct modes of runtime isolation:
Process Isolation & Hyper-V Isolation.
Because Windows containers can run in two distinct modes, you will need to install or
activate Hyper-V on the development machine.

Enable-WindowsOptionalFeature -Online -FeatureName Hyper-V : powershell.

In the Process Isolation mode, multiple containers run concurrently and share the same kernel with the host,
as with each other.

This approach is also how Linux containers run and is the more traditional approach.

However, this approach has a downside for Windows containers.
The base image operating system that is used within the
container should match the operating system of the host.
You can't run a container that is based on Windows Server 2016 on a Windows Server 2019 host,
and you certainly can't run a container based on Windows Server 2019 on a Windows Server 2016 host.

Hyper-V Isolation uses Microsoft Hyper-V to host the containers.
This mode offers enhanced security and better compatibility between the host operating system
and the container's base image operating system.
This mode will run a highly optimized virtual machine that will have its own kernel.
The container runs within that virtual machine.

Even with Hyper-V isolation, not all combinations are valid.
You still can't run a Windows Server 2019 container on a Windows Server 2016 host.
Need to check windows containers compatibility

Windows container version compatibility :
https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/version-compatibility/

docker run -it --isolation=hyperv mcr.microsoft.com/windows/servercore:ltsc2019 cmd

--isolation=hyperv

`