Windows 10: After VM's - Docker and Containerisations

This looks interesting

instead of running full blown VM's you just "Containerize" your application (whatever it is and on whatever platform) and run it within the Docker application.

Docker

I haven't understood it much so far but it looks very intriguing. Perhaps VMWARE and ORACLE should be getting worried if this stuff works. I believe even Ms is getting into the act with the AZURE cloud servers.

Cheers
jimbo

:)

 

High CPU utilisation after running a Hyper-V VM (insider build 14965, 14967, 14971)

On Windows 10 Pro insider build 14971.1000, after starting a Hyper-V VM the System process consumes and entire CPU, slowing down the system. Some other users also reported this on 14965 and
14967 builds (Running Docker For Windows causes High System CPU utilization · Issue #220 · docker/for-win).

Looking at the process with Process Explorer It looks like a single thread spinning on:

ntoskrnl.exe!RtlAvlInsertNodeEx+0x20b70

Another user reported spinning on (on a
14967 build):

ntoskrnl.exe!RtlClearBitsEx+0x1fa0

Is there a workaround/fix?

 

Frequent DRIVER_CORRUPTED_EXPOOL BSOD

Thanks so much for taking the time to have a look at this. vpnkit.exe is part of Docker. So I think it's fair to assume that is the cause of the issue. I am now trying out running a container with a different configuration in Docker and
see if the issue persists. I'll also ask the Docker forums if other people have similar issues.

Again, thanks for helping out.

 

No, not interesting. There are plenty of ways to run something on something-else using some abstraction layer.

Java for example. Or Android. Or IBM i.

 

Docker and similar is not virtualization so much as sandboxing. It doesn't get rid of the underlying kernel, but does allow you to sandbox the libraries and other frameworks so that you can have them run in their own container for security, as well as isolation purposes. So, for example, you could run multiple versions of Internet Explorer in separate containers, but you couldn't run a Linux application because that would require a Linux kernel.

The idea is that you can sort of create a "disk" image of all the components necessary for an application to run, including all of its configuration, and it just runs in it's container. You don't need to install it, and you don't need to worry about it conflicting with other apps (or users).

It's not going to replace virtualization, which is necessary to manage resources, like CPU's and memory.. but it can replace a lot of the things that people currently use Virtualization for, but don't really have to.. when all they really need is isolation.