6 ms·

This is our big problem. Our development "workstations" are virtualized in VMWare. That's incompatible with Hyper-V, so MS is locking us out of this technology.

runevault 7y ago
Modern VMWare still doesn't support Hyper-V? That's unfortunate to hear. My old version doesn't so I have to reboot anytime I want to get into my VMWare VMs, yet I'd made the (sounds to be incorrect) assumption that would be fixed in newer versions.
- CWuestefeld 7y ago
  I'm referring to an architecture with ESX server running the VMs. I'm not sure exactly which version. But we've tested it recently and found that using Linux Docker on Windows 10 still doesn't work.
  - kijiki 7y ago
    It should work if you enable nested virtualization in ESX. They call it VHV (Virtual Hardware-Assisted Virtualization).
- ocdtrekkie 7y ago
  My understanding is that it isn't so much "VMware doesn't support Hyper-V" but that "Hyper-V doesn't permit other virtualization platforms to run alongside it" and that may be less of a technical limitation than one might assume.
  - AdrianB1 7y ago
    Hyper-V works in nested virtualization, the limitation seems to be in VMware in this particular case.
signal11 7y ago
If your dev workstations are virtualized already, why not ask your tooling team to provide virtualized Linux workstations? If you deploy to Linux this is something they should provide anyway, for dev/prod parity.
rcarmo 7y ago
You can do what I do in WSL 1, which is to forward the Docker daemon port from the VM and point your local CLI to it via the TCP port. I've been doing that for years now (I originally built my own Docker client binary for the Mac and pointed it to a Linux box, did the same when I ran Parallels on my Mac, and still do it occasionally with ARM boxes at home). People forget that Docker was designed as a client-server solution, and that the server bit works fine. You can ask your sysadmins to set up a VMware instance running boot2docker and link it directly to your Windows workstation.

runevault 7y ago

Modern VMWare still doesn't support Hyper-V? That's unfortunate to hear. My old version doesn't so I have to reboot anytime I want to get into my VMWare VMs, yet I'd made the (sounds to be incorrect) assumption that would be fixed in newer versions.

CWuestefeld 7y ago
I'm referring to an architecture with ESX server running the VMs. I'm not sure exactly which version. But we've tested it recently and found that using Linux Docker on Windows 10 still doesn't work.
- kijiki 7y ago
  It should work if you enable nested virtualization in ESX. They call it VHV (Virtual Hardware-Assisted Virtualization).
ocdtrekkie 7y ago
My understanding is that it isn't so much "VMware doesn't support Hyper-V" but that "Hyper-V doesn't permit other virtualization platforms to run alongside it" and that may be less of a technical limitation than one might assume.
- AdrianB1 7y ago
  Hyper-V works in nested virtualization, the limitation seems to be in VMware in this particular case.

signal11 7y ago

If your dev workstations are virtualized already, why not ask your tooling team to provide virtualized Linux workstations? If you deploy to Linux this is something they should provide anyway, for dev/prod parity.

rcarmo 7y ago

You can do what I do in WSL 1, which is to forward the Docker daemon port from the VM and point your local CLI to it via the TCP port. I've been doing that for years now (I originally built my own Docker client binary for the Mac and pointed it to a Linux box, did the same when I ran Parallels on my Mac, and still do it occasionally with ARM boxes at home). People forget that Docker was designed as a client-server solution, and that the server bit works fine. You can ask your sysadmins to set up a VMware instance running boot2docker and link it directly to your Windows workstation.