Official Zabbix Dockerfiles
Go to file
2018-05-31 20:09:12 -07:00
agent Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
java-gateway Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
proxy-mysql Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
proxy-sqlite3 Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
server-mysql Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
server-pgsql Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
snmptraps Updated all Dockerfiles to make consistency 2018-05-31 19:02:46 -07:00
web-apache-mysql Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
web-apache-pgsql Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
web-nginx-mysql Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
web-nginx-pgsql Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
zabbix-appliance Merge remote-tracking branch 'origin/master' into trunk 2018-05-31 20:09:12 -07:00
.env_agent Added SourceIP and ListenIP params 2017-05-11 03:37:37 -07:00
.env_db_mysql Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_db_mysql_proxy Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_db_pgsql Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_java Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_prx Updated docker compose variables 2018-02-20 06:50:59 -08:00
.env_prx_mysql Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_prx_sqlite3 Added compose files for 2.0 2016-08-11 14:16:42 -07:00
.env_srv Updated docker compose variables 2018-02-20 06:50:59 -08:00
.env_web TZ env variable renamed to PHP_TZ to avoid confusing with system-wide envs 2017-05-22 12:34:39 +03:00
docker-compose_v2_alpine_mysql_latest.yaml Merge master 2018-05-10 16:38:07 -07:00
docker-compose_v2_alpine_mysql_local.yaml Updated Zabbix compose files to support Zabbix snmptraps based on different images (Alpine, CentOS) 2018-05-10 13:47:09 -07:00
docker-compose_v2_alpine_pgsql_latest.yaml Merge master 2018-05-10 16:38:07 -07:00
docker-compose_v2_alpine_pgsql_local.yaml Updated Zabbix compose files to support Zabbix snmptraps based on different images (Alpine, CentOS) 2018-05-10 13:47:09 -07:00
docker-compose_v2_centos_mysql_latest.yaml Merge master 2018-05-10 16:38:07 -07:00
docker-compose_v2_centos_mysql_local.yaml Updated Zabbix compose files to support Zabbix snmptraps based on different images (Alpine, CentOS) 2018-05-10 13:47:09 -07:00
docker-compose_v2_centos_pgsql_latest.yaml Merge master 2018-05-10 16:38:07 -07:00
docker-compose_v2_centos_pgsql_local.yaml Updated Zabbix compose files to support Zabbix snmptraps based on different images (Alpine, CentOS) 2018-05-10 13:47:09 -07:00
docker-compose_v2_ubuntu_mysql_latest.yaml Fixed issue with proxy-mysql image 2018-02-17 16:20:18 -08:00
docker-compose_v2_ubuntu_mysql_local.yaml Fixed issue with non UTF-8 symbols on MySQL 2017-10-20 17:51:54 +03:00
docker-compose_v2_ubuntu_pgsql_latest.yaml Fixed issue with proxy-mysql image 2018-02-17 16:20:18 -08:00
docker-compose_v2_ubuntu_pgsql_local.yaml Fixed issue with non UTF-8 symbols on MySQL for proxies 2017-10-20 18:01:12 +03:00
docker-compose_v3_alpine_mysql_latest.yaml Merge master 2018-05-10 16:38:07 -07:00
docker-compose_v3_alpine_mysql_local.yaml Updated Zabbix compose files to support Zabbix snmptraps based on different images (Alpine, CentOS) 2018-05-10 13:47:09 -07:00
docker-compose_v3_alpine_pgsql_latest.yaml Merge master 2018-05-10 16:38:07 -07:00
docker-compose_v3_alpine_pgsql_local.yaml Updated Zabbix compose files to support Zabbix snmptraps based on different images (Alpine, CentOS) 2018-05-10 13:47:09 -07:00
docker-compose_v3_centos_mysql_latest.yaml Merge master 2018-05-10 16:38:07 -07:00
docker-compose_v3_centos_mysql_local.yaml Updated Zabbix compose files to support Zabbix snmptraps based on different images (Alpine, CentOS) 2018-05-10 13:47:09 -07:00
docker-compose_v3_centos_pgsql_latest.yaml Merge master 2018-05-10 16:38:07 -07:00
docker-compose_v3_centos_pgsql_local.yaml Updated Zabbix compose files to support Zabbix snmptraps based on different images (Alpine, CentOS) 2018-05-10 13:47:09 -07:00
docker-compose_v3_ubuntu_mysql_latest.yaml Added v3 compose files 2018-02-20 06:44:19 -08:00
docker-compose_v3_ubuntu_mysql_local.yaml Added v3 compose files 2018-02-20 06:22:27 -08:00
docker-compose_v3_ubuntu_pgsql_latest.yaml Added v3 compose files 2018-02-20 06:44:19 -08:00
docker-compose_v3_ubuntu_pgsql_local.yaml Added v3 compose files 2018-02-20 06:22:27 -08:00
docker-entrypoint.sh Fixed small issues. Preparation for Appliance 2018-03-30 05:36:16 -07:00
kubernetes.yaml Fixed issue with proxy-mysql image 2018-02-17 16:20:18 -08:00
LICENSE Initial commit 2016-08-03 10:36:02 +03:00
README.md Fixed small issues. Preparation for Appliance 2018-03-30 06:19:06 -07:00

logo

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

Zabbix Dockerfiles

This repository contains Dockerfile of Zabbix for Docker's automated build published to the public Docker Hub Registry.

Base Docker Image

Usage

Please follow usage instructions of each Zabbix component image:

Issues

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

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.