clickbg / homekit-monitord

HomeKit Active Hub Monitoring with Monit and Nginx
BSD 2-Clause "Simplified" License
5 stars 0 forks source link

Container will not start #1

Closed PaRkThEcAr closed 2 years ago

PaRkThEcAr commented 2 years ago

Platform: macOS 12.3.1

Logs

Restarting daemon monitor: monit failed!
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf differs from the packaged version
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/99-homekit-monitoring-config.sh
/etc/monit/monitrc:13: missing address ''
Restarting daemon monitor: monit failed!

Configuration

version: '3.6'
services:

  homekit-monitord:
    container_name: homekit-monitord
    restart: always
    image: clickbg/homekit-monitord:latest
    ports:
      - "8080:80"
    environment:
      - PUID=1000
      - PGID=1000
      - RESTART_HUB=0
      - HOMEKIT_HUBS=192.168.1.20:200 192.168.1.21:200 192.168.1.22:200 192.168.1.25:200 192.168.1.27:200 192.168.1.28:200
      - TELEGRAM_TOKEN=SUPERSECRET
      - TELEGRAM_CHATID=SECRET
    healthcheck:
      test: curl --fail http://localhost/nginx_status || exit 1
      interval: 10s
      retries: 5
      start_period: 5s
      timeout: 10s

I cant seem to get the container to start

clickbg commented 2 years ago

Hi, thanks for the feedback!

I forgot to remove one monit property when the e-mail notifications are disabled. Fix is committed and new version of the container is available on DockerHub - https://github.com/clickbg/homekit-monitord/commit/602c7f309ebbf83661a2ff7b724ae1dbeaf6a69d

Please pull the new version with: docker-compose pull

And restart it with: docker-compose up -d --remove-orphans

PaRkThEcAr commented 2 years ago

Thanks! This works like a charm!