Public | Automated Build

Last pushed: 6 days ago
Short Description
HomeKit support for the impatient using Docker on x86_64 or Raspberry Pi (armhf)
Full Description

Docker Homebridge

This Alpine Linux based Docker image allows you to run Nfarina's Homebridge on your home network which emulates the iOS HomeKit API.



Homebridge requires full access to your local network to function correctly which can be achieved using the --net=host flag.
Currently this will not work when using Docker for Mac due to this issue.


docker run \
  --net=host \
  --name=homebridge \
  -e PUID=<UID> -e PGID=<GID> \
  -e TZ=<timezone> \
  -v </path/to/config>:/homebridge \

Raspberry Pi

This image will also run on a Raspberry Pi using the raspberry-pi tag:

docker run --net=host --name=homebridge oznu/homebridge:raspberry-pi

This docker image has been tested on the following Raspberry Pi models:

  • Raspberry Pi 1 Model B
  • Raspberry Pi 3 Model B
  • Raspberry Pi Zero W

See the wiki for a guide on getting Homebridge up and running on a Raspberry Pi.


The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side.

  • --net=host - Shares host networking with container, required
  • -v /homebridge - The Homebridge config and plugin location
  • -e TZ - for timezone information e.g. -e TZ=Europe/London
  • -e PGID - for for GroupID - see below for explanation
  • -e PUID - for for UserID - see below for explanation

Optional Settings:

  • -e PACKAGES - Additional packages to install (comma separated, no spaces) e.g. -e PACKAGES=ffmpeg,openssh

User / Group Identifiers

Sometimes when using data volumes (-v flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user PUID and group PGID. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work".

In this instance PUID=1001 and PGID=1001. To find yours use id user as below:

  $ id <dockeruser>
    uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

Homebridge Config

The Homebridge config file is located at </path/to/config>/config.json
This file will be created the first time you run the container if it does not already exist.

Homebridge Plugins

Plugins should be defined in the </path/to/config>/package.json file in the standard NPM format.
This file will be created the first time you run the container if it does not already exist.

Any plugins added to the package.json will be installed each time the container is restarted.
Plugins can be uninstalled by removing the entry from the package.json and restarting the container.

You can also install plugins using yarn (an npm replacement) which will automatically update the package.json file as you add and remove modules.

You must restart the container after installing or removing plugins for the changes to take effect.

To add plugins using yarn:

docker exec <container name or id> yarn add <module name>


docker exec homebridge yarn add homebridge-hue

To remove plugins using yarn:

docker exec <container name or id> yarn remove <module name>


docker exec homebridge yarn remove homebridge-hue

Docker Compose

If you prefer to use Docker Compose:

version: '2'
    image: oznu/homebridge
    restart: always
    network_mode: host
      - TZ=Australia/Sydney
      - PGID=911
      - PUID=911
      - ./volumes/homebridge:/homebridge


1. Verify your config.json and package.json syntax

Many issues appear because of invalid JSON. A good way to verify your config is to use the validator.

Docker Pull Command
Source Repository

Comments (0)