Use VMPal containers from inside a Windows guest VM #70

Description

Would it be possible to use VMPal's containers from inside a guest VM, especially Windows?

Since VMPal already supports containers and Docker commands, it would be great to run docker and docker compose from PowerShell inside a Windows VM and have them use VMPal's container engine on the Mac. The Linux containers would continue running through VMPal, with the Windows guest acting as the client.

For example, I'd like to:

1. Open a project in Visual Studio inside the Windows VM.
2. Start PostgreSQL, Redis, or other dependencies using Docker commands or Compose from the Windows terminal.
3. Connect my Windows application to those container services.
4. See and manage the same containers in VMPal on the Mac.

A simple option such as "Use VMPal containers" in the VM settings, with connection setup handled by VMPal Tools, would make this easy to get started with. It would also be helpful to have a straightforward way for Windows apps to reach the containers' published ports.

Why this feature/change is important?

This would make VMPal more convenient for development inside Windows VMs. Developers could keep their IDE and application in Windows while sharing the container engine VMPal already provides, without setting up Docker Desktop or another container runtime inside the guest.

It could also avoid running a second container engine and keeping separate copies of container images and dependencies.

This could also help VMPal stand out as an alternative to Parallels for Windows development on Apple silicon. Parallels currently documents that WSL 2 and nested virtualization are unavailable in its Windows guests on Apple silicon, with WSL 1 offered as a workaround. Parallels' Windows on Apple silicon limitations.

Access to VMPal's existing container engine from Windows would let developers work with Linux containers without depending on WSL 2 or nested virtualization inside the guest. That could make VMPal a more attractive choice for developers who want their IDE and applications in Windows, with easy access to containerized services.

Even an initial version focused on database and cache containers with named volumes would be useful. Sharing Windows project folders with containers could be a later improvement.