It would be awesome to support:
Supporting these would enable advanced network architectures, such as running a Linux routing VM with:
- A
VZFileHandleNetworkDeviceAttachment, allowing packets to be read and written from the host, and routed through a VPN. This is especially useful when LAN connections are blocked (Docker Desktop uses a similar approach with VPNKit1).
- A
VZVmnetNetworkDeviceAttachment, which can also be mounted on other VMs to allow them to access the internet via the Linux routing VM.
This would enable cleaner solutions compared to existing workarounds:
Note: #7380 did some work for VZVmnetNetworkDeviceAttachment.
It would be awesome to support:
macOS 26.0+)macOS 11.0+)Supporting these would enable advanced network architectures, such as running a Linux routing VM with:
VZFileHandleNetworkDeviceAttachment, allowing packets to be read and written from the host, and routed through a VPN. This is especially useful when LAN connections are blocked (Docker Desktop uses a similar approach with VPNKit1).VZVmnetNetworkDeviceAttachment, which can also be mounted on other VMs to allow them to access the internet via the Linux routing VM.This would enable cleaner solutions compared to existing workarounds:
Note: #7380 did some work for
VZVmnetNetworkDeviceAttachment.Footnotes
https://docs.docker.com/desktop/features/networking/#vpn-passthrough ↩