Running HomeBridge on Docker without Host Network Mode

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.

There is one older device that I have which does not support HomeKit, and was only controllable through the App from the manufacturer. HomeKit support for this device is not coming, but there is a workaround.

Enter HomeBridge.

HomeKit support for the impatient.

Homebridge is a lightweight NodeJS server you can run on your home network that emulates the iOS HomeKit API. 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.

There is a docker image available, but the setup instructions for this require the container to be ran with the “host” networking mode. 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.

For 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.

Required Ports & Configuration

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. 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 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.

  "bridge": {
    "name": "Homebridge",
    "username": "CC:22:3D:E3:CE:30",
    "port": 51826,
    "pin": "031-45-154"

If additional devices are being configured which require their own ports, then additional ports may be required. For devices which function this way, the HomeBridge configuration allows the range of ports which would be used to be specified.

	// other configuration omitted 
  "ports": {
    "start": 52100,
    "end": 52150,
    "comment": "This section is used to control the range of ports that separate accessory (like camera or television) should be bind to."

Advertising the HomeKit device

This was the most tricky part of this setup.

If we are not allowing the container to advertise its own “HAP” mDNS record, then we need to advertise it for it.

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.

Ultimately this involved some research into the HAP protocol, and how HomeBridge uses HAP-NodeJS to advertise the service.

The result is the linked bash script,, which inspects a running HomeBridge container for the required configuration it needs to generate an Avahi service file. This file is then moved to the /etc/avahi/services directory for use. This should be published without the need for a restart of the avahi-daemon.

Docker Compose

The complete docker compose file I am using (minus my Traefik labels) is below.

version: '3.7'

      name: traefik-backend



    image: oznu/homebridge:no-avahi
    restart: unless-stopped
     - traefik-backend
      - homebridge_config:/homebridge
      - /data-storage/app-data/homebridge/config.json:/homebridge/config.json
      - PGID=1099
      - PUID=1099
     # port matching config.json
     - 51826:51826/tcp

In Conclusion

It is possible to run HomeBridge in a Docker container without requiring to use the host networking mode, it just requires a bit of additional configuration of an Avahi service.