Unfortunately Hyper-V isn’t compatible with VMWare and VirtualBox so either you use Hyper-V and Docker for Windows or you deactivate Hyper-V and use Docker-Machine.
Luckily there are tools to convert from VMWare to Hyper-V and vice versa but I cannot tell how reliable they are.
If I want to continue with Docker for Windows I need to convert my other fee VMs. Does anyone has made a good experience with the above-referenced tool?
I would like to avoid experimenting in this matter as besides the clear advantages of Docker compared to a virtual machine I still have some desktop only application what cannot be replaced by docker (server) based applications.
It has been quite a while but better late than never. Here comes a rough guide on how to convert between VMWare and Hyper-V.
from VMWare to Hyper-V
If you don’t have VMWare server running you can only convert VMDK to VHD(X) using PowerShell. This (and the server variant) is described here:
Afterwards, you create a new Hyper-V VM using the converted virtual disk. Most likely you have to adapt boot security options https://www.notyourdadsit.com/blog/2018/2/24/hyper-v-error-the-images-hash-and-certificate-are-not-allowed
from Hyper-V to VMWare
That is quite simple as you can use the VMWare standalone converter. The only thing you have to do is to set the Local Security Policy setting for “User Account Control: Run all administrators in Admin Approval Mode” to Disabled, as described in https://communities.vmware.com/thread/531600 otherwise, you get VMware Converter: Permission to perform this operation was denied – Jonathan Medd’s Blog.
The login asked for during the convert job creations is the login of your local Windows machine.
Last but not least.
If you try to start the VM straight away you will get the error “VMware Workstation and Device/Credential Guard are not compatible” error in VMware Workstation on Windows 10 host (2146361)that tells you to deactivate [Windows Defender Credential Guard]https://docs.microsoft.com/en-gb/windows/security/identity-protection/credential-guard/credential-guard-manage#disable-windows-defender-credential-guard).
You still have to do this but there is hope read: