Virtual Machine Detected as soon as Docker is installedAnswered

Some customers have docker installed on their Windows machine. This is more and more common as people tend to install machine learning containers…

Problem is as soon as you installl docker, it enables Hypervisor. Turning it off means breaking docker engine… which is not a very good reply to give to customers.

Do you have another option in this case, besides allowing VM ? Maybe a more fine grain setting?

Answer

If they're in Hyper-V then they're in a VM.

Covered here: https://wyday.com/limelm/help/faq/#in-vm


There are multiple ways to run docker (including not in Hyper-V): https://stackoverflow.com/a/48252608/124805


And, of course, using TurboFloat is an option when running inside a VM. Covered in the FAQ.

Just saying this is the default that happens as soon as you install Docker for windows, which is what most people do. Then redirecting to a page that asks for entering admin commands in a terminal is a huge turn-off… 

I get your point of Turbofloat, but in our case this is for free trials. We dissallow VM, but we get many false positives, that it is diserving us more than anything. 

Asking our non paying customers to do all these admin tasks in order to try the product is not a great way to convert them into paying customers….

, edited

You can allow trials and activations inside VMs if you want. It's an option we give you.