For development on Windows 10 Pro, Boxfuse can run your apps on Hyper-V.
Boxfuse supports Hyper-V running on Windows 10 Pro.
Due to the way Hyper-V is architected, VirtualBox will no longer work if Hyper-V is enabled. If you need VirtualBox compatibility, you must disable Hyper-V to make VirtualBox work again.
You can control the number of CPUs exposed to the VM using the
cpus property and the number of MB of RAM
ram property. By default, Boxfuse assigns 2 CPUs and 1024 MB of RAM to the Instance.
Boxfuse creates a new public Hyper-V Virtual Switch on your external network interface.
To make it easy to access services running on your physical machine (outside of your Boxfuse Hyper-V instance),
Boxfuse exposes an environment variable named
BOXFUSE_HOST_IP to each of its Hyper-V instances. This environment
variable contains the IP address of your physical machine (example: 172.27.3.61) which you can use
this to construct URLs to access your services.
To make it easy to access AWS services from your VirtualBox instances, Boxfuse automatically exposes the AWS credentials stored by the AWS CLI on your local machine to the running instances.
Boxfuse will attempt to load credentials in the following order:
You can also manually override this by explicitly setting the