heimergroup/zabbix repository overview

⁠Introduction

The complete Zabbix monitoring solution consists of three images. Place all the images on the same network for easy linking. Be sure to create a volume for persistent DB storage.

⁠Tag description

The for the images corresponds to the Zabbix version with "latest" being the highest current version.

⁠Images in collection

• -dbs-server : PostgreSQL DB preloaded with the Zabbix tables. Based off of heimergroup/postgres⁠ image. See that repository for what the current DB version is. There is also a label inside of the image with the DB version.
• -app-server : This is the actual Zabbix application server.
• -web-server : Webserver using FastCGI to serve the Zabbix PHP files with PHP-FPM.

⁠Environment variables used by the images to create the containers

⁠DB server

• POSTGRES_USER : Set the database owner username, defaults to 'postgres' (via /docker-entrypoint.sh)
• POSTGRES_PASSWORD : Password used by the database owner (defaults no password)

There are others, but for proper Zabbix function you should not change them from the defaults unless needed.

⁠Using the images to setup the solution

⁠Create the network and database server container

docker network create zabbix

docker run -d -e POSTGRES_USER=zabbix \
-e POSTGRES_PASSWORD=zabbix --name zabbix-dbs \
--network zabbix --volume zabbix-dbs-data:/var/lib/pgsql \
heimergroup/zabbix:latest-dbs-server

Follow the logs to watch the install. The container will create the original DB owned by 'postgres' with either 'md5' as the auth method if you have supplied a password or 'trust' if you did not. It will then start the DB. If you supplied a different owner of the DB it will then DROP the original DB created and create a new one named for the owner. It will then load the Zabbix tables/data/etc. into the DB and then down a shutdown and then restart and run as the final step. Follow the install logs with:

docker logs -f zabbix-dbs

If you are using an existing DB data volume with a previous DB the DB creation steps will be skipped and start the DB process with the existing DB. If you are upgrading the container to use the existing volume always create a backup first! If the DB version itself is passing through a major upgrade you may need to do a dump and restore of the data as recommended by the PostgreSQL docs.