While I could have just captured the output of the container’s mDNS record and put it into a static service file, I wanted to be able to regenerate this if I ever scrapped the container and started again.
If we are not allowing the container to advertise its own “HAP” mDNS record, then we need to advertise it for it. This was the most tricky part of this setup. The main HomeBridge server port is defined in the config.json file, so if this port is mapped from the docker host to the container then HomeBridge will work, if it can be discovered. In my case I am using Traefik as a reverse proxy to front the web UI and enforce HTTPS in front of the web UI. The main HomeBridge server only requires one port to be exposed to function, with another optional one if you wish to use the web UI for it. The primary reason for this appears to be to allow an Avahi daemon to run in the container and be able to answer responses to mDNS requests, which requires the container to be in the same local network subnet as the device performing the lookup.įor isolation purposes I’m not a fan of running services in host networking mode, and I already have an avahi-daemon running on my server for advertising other services. There is a docker image available, but the setup instructions for this require the container to be ran with the “host” networking mode. It supports Plugins, which are community-contributed modules that provide a basic bridge from HomeKit to various 3rd-party APIs provided by manufacturers of “smart home” devices. Homebridge is a lightweight NodeJS server you can run on your home network that emulates the iOS HomeKit API. HomeKit support for this device is not coming, but there is a workaround. There is one older device that I have which does not support HomeKit, and was only controllable through the App from the manufacturer. Over the past few months I have been expanding the number of smart home devices I have and appreciating how HomeKit allows these to all be managed in a single place, regardless of the manufacturer. Running HomeBridge on Docker without Host Network Mode - Additional Accessories Running HomeBridge on Docker without Host Network Mode
DOCKER NETWORK MODE HOST PORT MAPPING SERIES
This post is part 1 of the series "Running HomeBridge on Docker without Host Network Mode".
0 kommentar(er)
