pdbs/icinga2 repository overview

⁠Icinga2 / Icingaweb2

including the most important modules, DB drivers & PHP

⁠Setup Token

setup token is printed to stdout after the SETUP TOKEN message. In a swarm environment display token with 'docker service logs '. During setup use icinga2 as database name ans postgres as user (without password - local connection)

⁠Docker Service (with traefik)

docker service create --name monitor
--label "traefik.frontend.rule=Host:"
--label "traefik.port=80"
--label 'traefik.enable=true'
--network clusternet
--mount type=bind,src=/cluster/container/monitor/etc,dst=/etc/apache2
--mount type=bind,src=/cluster/container/monitor/var,dst=/var/www
--mount type=bind,src=/cluster/container/monitor/log,dst=/var/log/apache2
--mount type=bind,src=/cluster/container/monitor/icinga,dst=/etc/icinga2
--mount type=bind,src=/cluster/container/monitor/icingaweb,dst=/etc/icingaweb2
--mount type=bind,src=/cluster/container/monitor/postgres,dst=/var/lib/postgresql
pdbs/icinga2:latest

⁠Docker Container

start docker container:

docker run -it -p 80:80 --name icinga2 pdbs/icinga2

⁠Upgrade Procedure

Upgrades can be made without re-initialization of the Icinga service. However, if something fails, follow the procedure as described below.

• Backup everything! An upgrade should be done on a fresh database installation. Icinga configuration is in icinga/conf.d/ and must be saved
• Stop service
• Remove contents of directories etc/* icinga/* icingaweb/* log/* postgres/* var/*
• Start service, new image should be pulled from Docker Hub
• 'docker service logs ' prints out setup token
• Open /icingaweb2 in browser and perform setup
• Database user & password are in icinga/features-enabled/ido-pgsql.conf
• Restore icinga/conf.d/ and chown to correct uid/gid

If something else fails (e.g. config file messed up), issue

/etc/init.d/icinga2 checkconfig

inside the container.