Running as root about docker-homebridge HOT 4 CLOSED

Did you run docker-compose up -d after changing the PGID and PUID in the docker-compose file?

version: '2'
services:
  homebridge:
    image: oznu/homebridge:latest  # use "raspberry-pi" instead of "latest" for arm devices
    restart: always
    network_mode: host
    environment:
      - PGID=0
      - PUID=0
    volumes:
      - ./volumes/homebridge:/homebridge

If docker-compose up -d doesn't work, run docker-compose down then docker-compose up -d.

from docker-homebridge.

Setting the PUID and PGID variables to 0 will run the homebridge process as root:

docker run --net=host -e PUID=0 -e PGID=0 oznu/homebridge

from docker-homebridge.

Sweet! That fixed it. Thanks a lot!

from docker-homebridge.

@oznu Sorry to dredge up an old issue, but I have an issue using the same plugin. I found that manually changing the PGID and PUID in the docker-compose.yml both to 0 doesn't seem to actually affect the process. In the logs it shows "User uid: 1000" and "User gid: 1000." This means I'm not able to actually get root access in the container. Is this something to do with docker-compose? Is there another way I should be doing it? I'm on Raspberry Pi if that makes any difference.

from docker-homebridge.