Current Situation

The wiki states here that Windows and macOS are not supported as they lack the --net=host parameter. This is no longer the case in Docker Desktop 4.34.0. Homebridge does indeed start and appears to function as expected with one minor issue, the detected IP addresses are that of the docker container itself, and not the host.

Proposed Change

Allow a configuration variable to force Homebridge to advertise itself on a given IP address even if it's not bound to it, this should allow HomeKit to find the Homeridge instance.

Additional Context

Docker Desktop documentation: https://docs.docker.com/engine/network/drivers/host/#docker-desktop