Public | Automated Build

Last pushed: 10 hours ago
Short Description
Zabbix frontend based on Nginx web-server with MySQL support
Full Description

What is Zabbix?

Zabbix is an enterprise-class open source distributed monitoring solution.

Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.

For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

What is Zabbix web interface?

Zabbix web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics.

Zabbix web interface images

These are the only official Zabbix web interface Docker images. They are based on latest Alpine and trusty Ubuntu images. The available versions of Zabbix web interface are:

Zabbix server 3.0 (tags: alpine-3.0-latest, ubuntu-3.0-latest)
Zabbix server 3.0.* (tags: alpine-3.0.*, ubuntu-3.0.*)
Zabbix server 3.2 (tags: alpine-3.2-latest, ubuntu-3.2-latest)
Zabbix server 3.2.* (tags: alpine-3.2.*, ubuntu-3.2.*)
Zabbix server 3.4 (tags: alpine-3.4-latest, ubuntu-3.4-latest, alpine-latest, ubuntu-latest, latest)
Zabbix server 3.4.* (tags: alpine-3.4.*, ubuntu-3.4.*)
Zabbix server 4.0 (tags: alpine-trunk, ubuntu-trunk)

Images are updated when new releases are published. The image with latest tag is based on Alpine Linux.

Zabbix web interface available in three editions:

  • Zabbix web-interface based on Apache2 web server with MySQL database support
  • Zabbix web-interface based on Apache2 web server with PostgreSQL database support
  • Zabbix web-interface based on Nginx web server with MySQL database support
  • Zabbix web-interface based on Nginx web server with PostgreSQL database support

The image based on Nginx web server with MySQL database support.

How to use this image

Start zabbix-web-nginx-mysql

Start a Zabbix web-interface container as follows:

docker run --name some-zabbix-web-nginx-mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER="some-user" -e MYSQL_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag

Where some-zabbix-web-nginx-mysql is the name you want to assign to your container, some-mysql-server is IP or DNS name of MySQL server, some-user is user to connect to Zabbix database on MySQL server, some-password is the password to connect to MySQL server, some-zabbix-server is IP or DNS name of Zabbix server or proxy, some-timezone is PHP like timezone name and tag is the tag specifying the version you want. See the list above for relevant tags, or look at the full list of tags.

Linking the container to Zabbix server

docker run --name some-zabbix-web-nginx-mysql --link some-zabbix-server:zabbix-server -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER="some-user" -e MYSQL_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag

Linking the container to MySQL database

docker run --name some-zabbix-web-nginx-mysql --link some-mysql-server:mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER="some-user" -e MYSQL_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag

Container shell access and viewing Zabbix web interface logs

The docker exec command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your zabbix-web-nginx-mysql container:

$ docker exec -ti some-zabbix-web-nginx-mysql /bin/bash

The Zabbix web interface log is available through Docker's container log:

$ docker logs  some-zabbix-web-nginx-mysql

Environment Variables

When you start the zabbix-web-nginx-mysql image, you can adjust the configuration of the Zabbix web interface by passing one or more environment variables on the docker run command line.

ZBX_SERVER_HOST

This variable is IP or DNS name of Zabbix server. By default, value is zabbix-server.

ZBX_SERVER_PORT

This variable is port Zabbix server listening on. By default, value is 10051.

DB_SERVER_HOST

This variable is IP or DNS name of MySQL server. By default, value is 'mysql-server'

DB_SERVER_PORT

This variable is port of MySQL server. By default, value is '3306'.

MYSQL_USER, MYSQL_PASSWORD

These variables are used by Zabbix web interface to connect to Zabbix database. By default, values are zabbix, zabbix.

MYSQL_DATABASE

The variable is Zabbix database name. By default, value is zabbix.

PHP_TZ

The variable is timezone in PHP format. Full list of supported timezones are available on php.net. By default, value is 'Europe/Riga'.

ZBX_SERVER_NAME

The variable is visible Zabbix installation name in right top corner of the web interface.

ZBX_MAXEXECUTIONTIME

The varable is PHP max_execution_time option. By default, value is 300.

ZBX_MEMORYLIMIT

The varable is PHP memory_limit option. By default, value is 128M.

ZBX_POSTMAXSIZE

The varable is PHP post_max_size option. By default, value is 16M.

ZBX_UPLOADMAXFILESIZE

The varable is PHP upload_max_filesize option. By default, value is 2M.

ZBX_MAXINPUTTIME

The varable is PHP max_input_time option. By default, value is 300.

Allowed volumes for the Zabbix web interface container

/etc/ssl/nginx

The volume allows to enable HTTPS for the Zabbix web interface. The volume must contains two files ssl.crt, ssl.key and dhparam.pem prepared for Nginx SSL connections.

Please follow official Nginx documentation to get more details about how to create certificate files.

The image variants

The zabbix-web-nginx-mysql images come in many flavors, each designed for a specific use case.

zabbix-web-nginx-mysql:ubuntu-<version>

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.

zabbix-web-nginx-mysql:alpine-<version>

This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.

This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.

To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).

Supported Docker versions

This image is officially supported on Docker version 1.12.0.

Support for older versions (down to 1.6) is provided on a best-effort basis.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

User Feedback

Documentation

Documentation for this image is stored in the web-nginx-mysql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

Issues

If you have any problems with or questions about this image, please contact us through a GitHub issue.

Known issues

Contributing

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Docker Pull Command
Owner
zabbix
Source Repository

Comments (6)
ffelixneto
6 days ago

yangchongduo
try to run
docker logs YOUR_DATABASE_CONTAINER
And see what is wrong with the connection ;)

yangchongduo
a month ago

Deploying Zabbix frontend (nginx) with mysql database Preparing the system
** Preparing Zabbix web-interface


  • DB_SERVER_HOST: some-mysql-server
  • DB_SERVER_PORT: 3306
  • DB_SERVER_DBNAME: zabbix
  • DB_SERVER_ZBX_USER: some-user
  • DB_SERVER_ZBX_PASS: some-password

MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...
MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...
MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...
MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...
MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...
MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...
MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...
MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...

yangchongduo
a month ago

Deploying Zabbix frontend (nginx) with mysql database Preparing the system
** Preparing Zabbix web-interface


  • DB_SERVER_HOST: some-mysql-server
  • DB_SERVER_PORT: 3306
  • DB_SERVER_DBNAME: zabbix
  • DB_SERVER_ZBX_USER: some-user
  • DB_SERVER_ZBX_PASS: some-password

MySQL server is not available. Waiting 5 seconds... MySQL server is not available. Waiting 5 seconds...

infinitylabs01
3 months ago

How test the email?

schrauber
4 months ago

There is a bug with setting the PHP timezone:
As documented above timezone should be taken from environment variable PHP_TZ,
but aktually it is taken from TZ.

fireice
8 months ago

nginx can not start.

Disable default vhosts Adding Zabbix virtual host (HTTP)
** Impossible to enable SSL support for Nginx. Certificates are missed. Preparing Zabbix frontend configuration file
Updating '/etc/php5/conf.d/99-zabbix.ini' parameter "max_execution_time": '600'... updated Updating '/etc/php5/conf.d/99-zabbix.ini' parameter "memory_limit": '128M'... updated
Updating '/etc/php5/conf.d/99-zabbix.ini' parameter "post_max_size": '16M'... updated Updating '/etc/php5/conf.d/99-zabbix.ini' parameter "upload_max_filesize": '2M'... updated
Updating '/etc/php5/conf.d/99-zabbix.ini' parameter "max_input_time": '300'... updated Updating '/etc/php5/conf.d/99-zabbix.ini' parameter "date.timezone": 'Europe/Riga'... added
** Cleaning the system

########################################################
* Executing supervisord
2017-03-03 06:43:11,479 CRIT Set uid to user 0
2017-03-03 06:43:11,479 CRIT Set uid to user 0
2017-03-03 06:43:11,479 WARN Included extra file "/etc/supervisor/conf.d/supervisord_zabbix.conf" during parsing
2017-03-03 06:43:11,479 WARN Included extra file "/etc/supervisor/conf.d/supervisord_zabbix.conf" during parsing
2017-03-03 06:43:11,485 INFO RPC interface 'supervisor' initialized
2017-03-03 06:43:11,485 INFO RPC interface 'supervisor' initialized
2017-03-03 06:43:11,485 INFO supervisord started with pid 1
2017-03-03 06:43:11,485 INFO supervisord started with pid 1
2017-03-03 06:43:12,487 INFO spawned: 'nginx' with pid 47
2017-03-03 06:43:12,487 INFO spawned: 'nginx' with pid 47
2017-03-03 06:43:12,488 INFO spawned: 'php-fpm' with pid 48
2017-03-03 06:43:12,488 INFO spawned: 'php-fpm' with pid 48
2017/03/03 06:43:12 [emerg] 47#47: open() "/etc/nginx/conf.d/default.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:62
nginx: [emerg] open() "/etc/nginx/conf.d/default.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:62
2017-03-03 06:43:12,496 INFO exited: nginx (exit status 1; not expected)
2017-03-03 06:43:12,496 INFO exited: nginx (exit status 1; not expected)
[03-Mar-2017 06:43:12] WARNING: Nothing matches the include pattern '/etc/php5/fpm.d/
.conf' from /etc/php5/php-fpm.conf at line 15.
2017-03-03 06:43:13,515 INFO spawned: 'nginx' with pid 51
2017-03-03 06:43:13,515 INFO spawned: 'nginx' with pid 51
2017-03-03 06:43:13,515 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-03 06:43:13,515 INFO success: php-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017/03/03 06:43:13 [emerg] 51#51: open() "/etc/nginx/conf.d/default.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:62
nginx: [emerg] open() "/etc/nginx/conf.d/default.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:62
2017-03-03 06:43:13,534 INFO exited: nginx (exit status 1; not expected)
2017-03-03 06:43:13,534 INFO exited: nginx (exit status 1; not expected)
2017-03-03 06:43:15,539 INFO spawned: 'nginx' with pid 52
2017-03-03 06:43:15,539 INFO spawned: 'nginx' with pid 52
2017/03/03 06:43:15 [emerg] 52#52: open() "/etc/nginx/conf.d/default.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:62
nginx: [emerg] open() "/etc/nginx/conf.d/default.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:62
2017-03-03 06:43:15,564 INFO exited: nginx (exit status 1; not expected)
2017-03-03 06:43:15,564 INFO exited: nginx (exit status 1; not expected)
2017-03-03 06:43:18,569 INFO spawned: 'nginx' with pid 53
2017-03-03 06:43:18,569 INFO spawned: 'nginx' with pid 53
2017/03/03 06:43:18 [emerg] 53#53: open() "/etc/nginx/conf.d/default.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:62
nginx: [emerg] open() "/etc/nginx/conf.d/default.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:62
2017-03-03 06:43:18,595 INFO exited: nginx (exit status 1; not expected)
2017-03-03 06:43:18,595 INFO exited: nginx (exit status 1; not expected)
2017-03-03 06:43:19,596 INFO gave up: nginx entered FATAL state, too many start retries too quickly
2017-03-03 06:43:19,596 INFO gave up: nginx entered FATAL state, too many start retries too quickly