�����IJ�

5 Installation from containers

Docker

�����IJ� provides images for each �����IJ� component as portable and self-sufficient containers to speed up deployment and update procedure.

�����IJ� components come with MySQL and PostgreSQL database support, Apache2 and Nginx web server support. These images are separated into different images.

Docker base images

�����IJ� components are provided on Ubuntu and Alpine Linux base images:

All images are configured to rebuild latest images if base images are updated.

Docker file sources

Everyone can follow Docker file changes using the �����IJ� on . You can fork the project or make your own images based on official Docker files.

Structure

All �����IJ� components are available in the following Docker repositories:

• �����IJ� agent -
• �����IJ� server
  • �����IJ� server with MySQL database support -
  • �����IJ� server with PostgreSQL database support -
• �����IJ� web-interface
  • �����IJ� web-interface based on Apache2 web server with MySQL database support -
  • �����IJ� web-interface based on Nginx web server with MySQL database support -
  • �����IJ� web-interface based on Nginx web server with PostgreSQL database support -
• �����IJ� proxy
  • �����IJ� proxy with SQLite3 database support -
  • �����IJ� proxy with MySQL database support -
• �����IJ� Java Gateway -

Additionally there is SNMP trap support. It is provided as additional repository () based on Ubuntu Trusty only. It could be linked with �����IJ� server and �����IJ� proxy.

Versions

Each repository of �����IJ� components contains the following tags:

• latest - latest stable version of a �����IJ� component based on Alpine Linux image
• alpine-latest - latest stable version of a �����IJ� component based on Alpine Linux image
• ubuntu-latest - latest stable version of a �����IJ� component based on Ubuntu image
• alpine-3.2-latest - latest minor version of a �����IJ� 3.2 component based on Alpine Linux image
• ubuntu-3.2-latest - latest minor version of a �����IJ� 3.2 component based on Ubuntu image
• alpine-3.2.* - different minor versions of a �����IJ� 3.2 component based on Alpine Linux image, where * is the minor version of �����IJ� component
• ubuntu-3.2.* - different minor versions of a �����IJ� 3.2 component based on Ubuntu image, where * is the minor version of �����IJ� component

Usage

Environment variables

All �����IJ� component images provide environment variables to control configuration. These environment variables are listed in each component repository. These environment variables are options from �����IJ� configuration files, but with different naming method. For example, ZBX_LOGSLOWQUERIES is equal to LogSlowQueries from �����IJ� server and �����IJ� proxy configuration files.

Some of components have specific environment variables, which do not exist in official �����IJ� configuration files:

Volumes

The images allow to use some mount points. These mount points are different and depend on �����IJ� component type:

For additional information use �����IJ� official repositories in Docker Hub.

Usage examples

** Example 1 **

The example demonstrates how to run �����IJ� server with MySQL database support, �����IJ� web interface based on the Nginx web server and �����IJ� Java gateway.

1. Start empty MySQL server instance

# docker run --name mysql-server -t \
             -e MYSQL_DATABASE="zabbix" \
             -e MYSQL_USER="zabbix" \
             -e MYSQL_PASSWORD="zabbix_pwd" \
             -e MYSQL_ROOT_PASSWORD="root_pwd" \
             -d mysql:5.7 \
             --character-set-server=utf8 --collation-server=utf8_bin

2. Start �����IJ� Java gateway instance

# docker run --name zabbix-java-gateway -t \
             -d zabbix/zabbix-java-gateway:latest

3. Start �����IJ� server instance and link the instance with created MySQL server instance

# docker run --name zabbix-server-mysql -t \
             -e DB_SERVER_HOST="mysql-server" \
             -e MYSQL_DATABASE="zabbix" \
             -e MYSQL_USER="zabbix" \
             -e MYSQL_PASSWORD="zabbix_pwd" \
             -e MYSQL_ROOT_PASSWORD="root_pwd" \
             -e ZBX_JAVAGATEWAY="zabbix-java-gateway" \
             --link mysql-server:mysql \
             --link zabbix-java-gateway:zabbix-java-gateway \
             -p 10051:10051 \
             -d zabbix/zabbix-server-mysql:latest

4. Start �����IJ� web interface and link the instance with created MySQL server and �����IJ� server instances

# docker run --name zabbix-web-nginx-mysql -t \
             -e DB_SERVER_HOST="mysql-server" \
             -e MYSQL_DATABASE="zabbix" \
             -e MYSQL_USER="zabbix" \
             -e MYSQL_PASSWORD="zabbix_pwd" \
             -e MYSQL_ROOT_PASSWORD="root_pwd" \
             --link mysql-server:mysql \
             --link zabbix-server-mysql:zabbix-server \
             -p 80:80 \
             -d zabbix/zabbix-web-nginx-mysql:latest

** Example 2 **

The example demonstrates how to run �����IJ� server with PostgreSQL database support, �����IJ� web interface based on the Nginx web server and SNMP trap feature.

1. Start empty PostgreSQL server instance

# docker run --name postgres-server -t \
             -e POSTGRES_USER="zabbix" \
             -e POSTGRES_PASSWORD="zabbix" \
             -e POSTGRES_DB="zabbix_pwd" \
             -d postgres:latest

2. Start �����IJ� snmptraps instance

# docker run --name zabbix-snmptraps -t \
             -v /zbx_instance/snmptraps:/var/lib/zabbix/snmptraps:rw \
             -v /var/lib/zabbix/mibs:/usr/share/snmp/mibs:ro \
             -p 162:162/udp \
             -d zabbix/zabbix-snmptraps:latest

3. Start �����IJ� server instance and link the instance with created PostgreSQL server instance

# docker run --name zabbix-server-pgsql -t \
             -e DB_SERVER_HOST="postgres-server" \
             -e POSTGRES_USER="zabbix" \
             -e POSTGRES_PASSWORD="zabbix" \
             -e POSTGRES_DB="zabbix_pwd" \
             -e ZBX_ENABLE_SNMP_TRAPS="true" \
             --link postgres-server:postgres \
             -p 10051:10051 \
             --volumes-from zabbix-snmptraps \
             -d zabbix/zabbix-server-pgsql:latest

4. Start �����IJ� web interface and link the instance with created PostgreSQL server and �����IJ� server instances

# docker run --name zabbix-web-nginx-pgsql -t \
             -e DB_SERVER_HOST="postgres-server" \
             -e POSTGRES_USER="zabbix" \
             -e POSTGRES_PASSWORD="zabbix" \
             -e POSTGRES_DB="zabbix_pwd" \
             --link postgres-server:postgres \
             --link zabbix-server-pgsql:zabbix-server \
             -p 443:443 \
             -v /etc/ssl/nginx:/etc/ssl/nginx:ro \
             -d zabbix/zabbix-web-nginx-pgsql:latest

Docker Compose

�����IJ� provides compose files also for defining and running multi-container �����IJ� components in Docker. These compose files are available in �����IJ� docker official repository on github.com: . These compose files are added as examples, they are overloaded. For example, they contain proxies with MySQL and SQLite3 support.

There are a few different versions of compose files:

Storage

Compose files are configured to support local storage on a host machine. Docker Compose will create a zbx_env directory in the folder with the compose file when you run �����IJ� components using the compose file. The directory will contain the same structure as described above in the Volumes section and directory for database storage.

There are also volumes in read-only mode for /etc/localtime and /etc/timezone files.

Environment files

In the same directory with compose files on github.com you can find files with default environment variables for each component in compose file. These environment files are named like .env_<type of component>.

Examples

** Example 1 **

# docker-compose -f ./docker-compose_v2_alpine_mysql_latest.yaml up -d

The command will download latest �����IJ� 3.2 images for each �����IJ� component and run them in detach mode.

** Example 2 **

# docker-compose -f ./docker-compose_v2_ubuntu_mysql_local.yaml up -d

The command will download base image Ubuntu 14.04, then build �����IJ� 3.2 components locally and run them in detach mode.