Zabbix Web Nginx MySQL Docker Image

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 [***]

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 Alpine Linux v3.24, Ubuntu 26.04 (resolute), CentOS Stream 10 and Oracle Linux 10 images. The available versions of Zabbix web interface are:

Zabbix web interface 6.0 (tags: alpine-6.0-latest, ubuntu-6.0-latest, ol-6.0-latest)
Zabbix web interface 6.0.* (tags: alpine-6.0.*, ubuntu-6.0.*, ol-6.0.*)
Zabbix web interface 7.0 (tags: alpine-7.0-latest, ubuntu-7.0-latest, ol-7.0-latest)
Zabbix web interface 7.0.* (tags: alpine-7.0.*, ubuntu-7.0.*, ol-7.0.*)
Zabbix web interface 7.4 (tags: alpine-7.4-latest, ubuntu-7.4-latest, ol-7.4-latest, alpine-latest, ubuntu-latest, ol-latest, latest)
Zabbix web interface 7.4.* (tags: alpine-7.4.*, ubuntu-7.4.*, ol-7.4.*)
Zabbix web interface 8.0 (tags: alpine-trunk, ubuntu-trunk, ol-trunk)

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

Zabbix web interface available in four 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 https://hub.docker.com/r/zabbix/zabbix-web-nginx-mysql/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:

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

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

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

Entrypoint hooks

Before starting the service, the image runs user-provided hooks from /etc/zabbix/entrypoint.d in filename order. Files ending in .sh are run with /bin/sh; other regular files are run directly when executable. Unsupported files are skipped. A failing hook stops container startup. Hooks inherit the container environment.

Mount the directory read-only with -v ./entrypoint.d:/etc/zabbix/entrypoint.d:ro.

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, MYSQL_USER_FILE, MYSQL_PASSWORD_FILE

These variables are used by Zabbix web-interface to connect to Zabbix database. With the _FILE variables you can instead provide the path to a file which contains the user / the password instead. Without Docker Swarm or Kubernetes you also have to map the files. Those are exclusive so you can just provide one type - either MYSQL_USER or MYSQL_USER_FILE!

console
docker run --name some-zabbix-web-nginx-mysql -e DB_SERVER_HOST="some-mysql-server" -v ./.MYSQL_USER:/run/secrets/MYSQL_USER -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER -v ./.MYSQL_PASSWORD:/run/secrets/MYSQL_PASSWORD -e MYSQL_PASSWORD_FILE=/var/run/secrets/MYSQL_PASSWORD -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag

With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!

console
printf "zabbix" | docker secret create MYSQL_USER -
printf "zabbix" | docker secret create MYSQL_PASSWORD -
docker run --name some-zabbix-web-nginx-mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER -e MYSQL_PASSWORD_FILE=/run/secrets/MYSQL_PASSWORD -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag

By default, values for MYSQL_USER and MYSQL_PASSWORD are zabbix, zabbix.

MYSQL_DATABASE

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

ZBX_HISTORYPROVIDER_<0-N>

History storage provider configuration in JSON format. Use consecutive indices starting with 0.

For ClickHouse, credentials can be set with the matching _USERNAME and _PASSWORD variables or their _FILE alternatives.

ZBX_TELEMETRYPROVIDER_0

ClickHouse telemetry provider configuration in JSON format.

Credentials and the TLS private key password can be set with the matching _USERNAME, _PASSWORD, and _SSL_KEY_PASSWORD variables or their _FILE alternatives.

Certificate and key paths may be absolute or relative to /var/lib/zabbix/ssl/certs and /var/lib/zabbix/ssl/keys, respectively. CA certificates are read from /var/lib/zabbix/ssl/ssl_ca.

ZBX_APM_CAFILE, ZBX_APM_CA

ZBX_APM_CAFILE specifies the CA file used as the default for APM providers. A relative path is resolved against /var/lib/zabbix/ssl/ssl_ca. Alternatively, ZBX_APM_CA provides the CA certificate content directly.

PHP_TZ

The variable is timezone in PHP format. Full list of supported timezones are available on http://php.net/manual/en/timezones.php. By default, value is 'Europe/Riga' and system timezone since Zabbix 5.2.0.

ZBX_SERVER_NAME

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

ZBX_DB_DOUBLE_IEEE754

Use IEEE754 compatible value range for 64-bit Numeric (float) history values. Available since 5.0.0. Enabled by default.

ENABLE_WEB_ACCESS_LOG

The variable sets the Access Log directive for Web server. By default, value corresponds to standard output.

HTTP_INDEX_FILE

The variable controls default index page. By default, index.php.

EXPOSE_WEB_SERVER_INFO

The variable allows to hide Web server and PHP versions. By default, on.

ZBX_MAXEXECUTIONTIME

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

ZBX_MEMORYLIMIT

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

ZBX_POSTMAXSIZE

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

ZBX_UPLOADMAXFILESIZE

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

ZBX_MAXINPUTTIME

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

ZBX_SESSION_NAME

The variable is Zabbix frontend definition. String used as the name of the Zabbix frontend session cookie. By default, value is zbx_sessionid.

ZBX_DENY_GUI_ACCESS

Enable (true) maintenance mode for Zabbix web-interface.

ZBX_GUI_ACCESS_IP_RANGE

Array of IP addresses which are allowed for accessing to Zabbix web-interface during maintenance period.

ZBX_GUI_WARNING_MSG

Information message about maintenance period for Zabbix web-interface.

ZBX_DB_ENCRYPTION

The variable allows to activate encryption for connections to Zabbix database. Even if no other environment variables are specified, connections will be TLS-encrypted if ZBX_DB_ENCRYPTION=true specified. Available since 5.0.0. Disabled by default.

ZBX_DBTLSKEYFILE

The variable allows to specify a TLS key file. Available since 5.0.0.

ZBX_DBTLSCERTFILE

The variable allows to specify a TLS certificate file. Available since 5.0.0.

ZBX_DBTLSCAFILE

The variable allows to specify a TLS certificate authority file. Available since 5.0.0.

ZBX_DB_VERIFY_HOST

The variable allows to activate host verification. Available since 5.0.0.

ZBX_DBTLSCIPHER

The variable allows to specify a custom list of valid ciphers. The format of the cipher list must conform to the OpenSSL standard. Available since 5.0.0.

ZBX_SSO_SP_KEYFILE, ZBX_SSO_SP_KEY

ZBX_SSO_SP_KEYFILE specifies the Service Provider (SP) private key file. A relative path is resolved against /etc/zabbix/web/certs. Alternatively, ZBX_SSO_SP_KEY provides the private key content directly. Available since 8.0.0.

ZBX_SSO_SP_CERTFILE, ZBX_SSO_SP_CERT

ZBX_SSO_SP_CERTFILE specifies the Service Provider (SP) certificate file. A relative path is resolved against /etc/zabbix/web/certs. Alternatively, ZBX_SSO_SP_CERT provides the certificate content directly. Available since 8.0.0.

ZBX_SSO_IDP_CERTFILE, ZBX_SSO_IDP_CERT

ZBX_SSO_IDP_CERTFILE specifies the Identity Provider (IdP) certificate file. A relative path is resolved against /etc/zabbix/web/certs. Alternatively, ZBX_SSO_IDP_CERT provides the certificate content directly. Available since 8.0.0.

ZBX_SSO_SETTINGS

The variable allows to specify custom SSO settings in JSON format. Available since 5.0.0.

Example of YAML Mapping to Sequences

....
  environment:
    ZBX_SSO_SETTINGS: "{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}"
    ....
....

ZBX_HTTP_AUTH_ENABLED

The variable allows to disable user HTTP authentication.

Other variables

Additionally the image allows to specify many other environment variables listed below:

ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
ZBX_VAULTDBPATH= # Available since 5.2.0
ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
VAULT_TOKEN= # Available since 5.2.0
ZBX_VAULTAPPROLEID= # Available since 8.0.0
ZBX_VAULTAPPSECRETID= # Available since 8.0.0
ZBX_VAULTPREFIX= # Available since 7.0.0
ZBX_VAULTTLSCERTFILE= # Available since 6.2.0
ZBX_VAULTTLSKEYFILE= # Available since 6.2.0
ZBX_VAULTCACHE=false # Available since 6.2.0

ZBX_CERT_STORAGE=database # Available since 8.0.0
ZBX_BANNERS_ENABLED=true # Available since 8.0.0
ZBX_MODULES_CONFIG_ENABLED=true # Available since 8.0.0
ZBX_MEDIA_TYPE_DENYLIST=[] # Available since 8.0.0

ZBX_APM_CAFILE= # Available since 8.0.0
ZBX_APM_CA= # Available since 8.0.0

ZBX_SSO_SP_KEYFILE= # Available since 8.0.0
ZBX_SSO_SP_KEY= # Available since 8.0.0
ZBX_SSO_SP_CERTFILE= # Available since 8.0.0
ZBX_SSO_SP_CERT= # Available since 8.0.0
ZBX_SSO_IDP_CERTFILE= # Available since 8.0.0
ZBX_SSO_IDP_CERT= # Available since 8.0.0

ZBX_SERVER_TLS_ACTIVE=false # Available since 7.4.0
ZBX_SERVER_TLS_CAFILE= # Available since 7.4.0
ZBX_SERVER_TLS_CA= # Available since 7.4.0
ZBX_SERVER_TLS_KEYFILE= # Available since 7.4.0
ZBX_SERVER_TLS_KEY= # Available since 7.4.0
ZBX_SERVER_TLS_CERTFILE= # Available since 7.4.0
ZBX_SERVER_TLS_CERT= # Available since 7.4.0
ZBX_SERVER_TLS_CERT_ISSUER= # Available since 7.4.0
ZBX_SERVER_TLS_CERT_SUBJECT= # Available since 7.4.0

Allowed PHP-FPM configuration options:
PHP_FPM_PM=dynamic
PHP_FPM_PM_MAX_CHILDREN=50
PHP_FPM_PM_START_SERVERS=5
PHP_FPM_PM_MIN_SPARE_SERVERS=5
PHP_FPM_PM_MAX_SPARE_SERVERS=35
PHP_FPM_PM_MAX_REQUESTS=0

Allowed Nginx configuration options:
WEB_REAL_IP_FROM=
WEB_REAL_IP_HEADER=

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 contain three files ssl.crt, ssl.key and dhparam.pem prepared for Nginx SSL connections.

Please follow official Nginx http://nginx.org/en/docs/http/configuring_https_servers.html to get more details about how to create certificate files.

/etc/zabbix/web/certs

The volume provides certificate and key files referenced by ZBX_SSO_SP_KEYFILE, ZBX_SSO_SP_CERTFILE, ZBX_SSO_IDP_CERTFILE, ZBX_VAULTTLSCERTFILE and ZBX_VAULTTLSKEYFILE. Relative paths are resolved against this directory. Available since 5.0.0.

/var/lib/zabbix/enc

The volume is used to store TLS related files. These file names are specified using ZBX_SERVER_TLS_CAFILE, ZBX_SERVER_TLS_KEYFILE and ZBX_SERVER_TLS_CERTFILE variables. Additionally it is possible to use environment variables ZBX_SERVER_TLS_CA, ZBX_SERVER_TLS_KEY and ZBX_SERVER_TLS_CERT with plaintext values. Available since 7.4.0.

/var/lib/zabbix/ssl/ssl_ca

The volume is used to provide certificate authority (CA) files for APM server certificate verification. The files are copied to an internal writable directory where OpenSSL hash links are generated before Zabbix frontend starts. The volume should be mounted read-only.

The image variants

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

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

This image is based on the popular [***] available in https://hub.docker.com/_/alpine. 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 http://www.musl-libc.org instead of http://www.etalabs.net/compare_libcs.html, 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 https://hub.docker.com/_/alpine/ for examples of how to install packages if you are unfamiliar).

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:ol-<version>

Oracle Linux is an open-source operating system available under the GNU General Public License (GPLv2). Suitable for general purpose or Oracle workloads, it benefits from rigorous testing of more than 128,000 hours per day with real-world workloads and includes unique innovations such as Ksplice for zero-downtime kernel patching, DTrace for real-time diagnostics, the powerful Btrfs file system, and more.

User Feedback

Documentation

Documentation for this image is stored in the https://github.com/zabbix/zabbix-docker/tree/trunk/Dockerfiles/web-nginx-mysql of the https://github.com/zabbix/zabbix-docker/. Be sure to familiarize yourself with the https://github.com/zabbix/zabbix-docker/blob/trunk/README.md before attempting a pull request.

Issues

If you have any problems with or questions about this image, please contact us through a https://github.com/zabbix/zabbix-docker/issues.

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 https://github.com/zabbix/zabbix-docker/issues, 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.

License

Starting from Zabbix version 7.0, all subsequent Zabbix versions will be released under the GNU Affero General Public License version 3 (AGPLv3). You can modify the relevant version and propagate such modified version under the terms of the AGPLv3 as published by the Free Software Foundation. For additional details, including answers to common questions about the AGPLv3, see the generic FAQ from the http://www.fsf.org/licenses/gpl-faq.html.

Zabbix is Open Source Software, however, if you use Zabbix in a commercial context we kindly ask you to support the development of Zabbix by purchasing some level of technical support. All previous Zabbix software versions up to 6.4 are released under the GNU General Public License version 2 (GPLv2). The formal terms of the GPLv2 and AGPLv3 can be found at http://www.fsf.org/licenses/.