[server 20303] Issues running containers

doctordns 

docker run hello-world --isolation-hyperv

should be

docker run --isolation=hyperv hello-world

Things after the container name are taken as parameters to the container execution, and so docker isn't seeing the "--isolation-hyperv" parameter when you add it, or it would have told you that it was an unknown parameter, as it needs to be "--isolation=hyperv" or "--isolation hyperv".

The hello-world container will need to run with Hyper-V isolation for you, because https://github.com/docker-library/hello-world/blob/master/amd64/hello-world/nanoserver-1809/Dockerfile, i.e. Windows Server LTSC 2019. If you're following a guide for Windows 10, note that on Windows 10, Hyper-V isolation is the default for Docker, so they won't use --isolation=hyperv in examples like this.

To use process isolation, you'll need to use an insider container image base matching the installed build, e.g. https://hub.docker.com/_/microsoft-windows-nanoserver-insider . Sadly, I don't think many (or any) image sources in the wild produce builds based on the insider versions, so if you're not building your own containers, you'll need to use Hyper-V isolation until this version of Windows Server is shipped, and container builders add it to their CI pipelines.