Zabbix Docker container which provides the Zabbix Server, Agent, Agent2, Webservice, Frontend.
6.6K
Container Source - GitHub Mirror
This is the Conarx Containers Zabbix image, it provides the Zabbix server, proxy, agent and agent2 services.
| Provider | Repository |
|---|---|
| DockerHub | allworldit/zabbix |
| Conarx | registry.conarx.tech/containers/zabbix |
All our Docker images are part of our Conarx Containers product line. Images are generally based on Alpine Linux and track the
Alpine Linux major and minor version in the format of vXX.YY.
Images built from source track both the Alpine Linux major and minor versions in addition to the main software component being
built in the format of vXX.YY-AA.BB, where AA.BB is the main software component version.
Our images are built using our Flexible Docker Containers framework which includes the below features...
Please use the project Issue Tracker.
Commercial support for all our Docker images is available from Conarx.
We also provide consulting services to create and maintain Docker images to meet your exact needs.
Additional environment variables are available from...
Mode for Zabbix to operate in, either server, proxy, agent or agent2.
Zabbix admin username to setup on first run. Defaults to 'Admin'.
Zabbix admin password to use for the ZABBIX_ADMIN_USERNAME on first run.
If set, the username and password are changed when the database is created.
Zabbix server agent name. The Zabbix server runs its own internal agent, this is the name configured for that agent, both of which must match. Defaults to 'Zabbix Server'.
Zabbix web service URL, used for generating reports. eg. http://localhost:10053/report.
Zabbix database type, either mysql, postgresql or timescaledb.
Database credentials if ZABBIX_DATABASE_TYPE is set to mysql.
Database credentials if ZABBIX_DATABASE_TYPE is set to postgresql or timescaledb.
List of IPv4, IPv6 or hostnames allowed to access the web service.
Proxy hostname configured in Zabbix.
Zabbix server hostname.
When specified, traffic between the proxy and server is encrypted.
The identity can be generated using pwmake 256.
The presharked key can be generated using openssl rand -hex 256.
Mode in which the proxy will operate, either 'active' or 'passive'.
Zabbix database type, either mysql, postgresql. NB. Timescaledb is not supported for proxies.
Database credentials if ZABBIX_DATABASE_TYPE is set to mysql.
Database credentials if ZABBIX_DATABASE_TYPE is set to postgresql or timescaledb.
Zabbix server hostname, defaults to 'zabbix-server'.
Name of the agent running on the Zabbix server. Defaults to 'Zabbix server'.
Zabbix database type, either mysql, postgresql. NB. Timescaledb is not supported for proxies.
Database credentials if ZABBIX_DATABASE_TYPE is set to mysql.
Database credentials if ZABBIX_DATABASE_TYPE is set to postgresql or timescaledb.
Optional. Use Zabbix proxy headers for SSO. Set to yes to enable.
Zabbix agent name setup on the server.
Zabbix agent mode, either 'active' or 'passive'.
When specified, traffic between the proxy and server is encrypted.
The identity can be generated using pwmake 256.
The presharked key can be generated using openssl rand -hex 256.
Zabbix agent name setup on the server.
Zabbix agent mode, either 'active' or 'passive'.
When specified, traffic between the proxy and server is encrypted.
The identity can be generated using pwmake 256.
The presharked key can be generated using openssl rand -hex 256.
Custom Zabbix config options, where option=value will be output.
For example ZABBIX_CONFIG_Hostname=abc becomes Hostname=abc.
Zabbix server configuration.
Zabbix server external scripts.
Zabbix server alert scripts.
SSH private keys should be named id_* and public keys should be named id_*.pub respectively. This ensures the correct
permissions will be set to prevent unauthorized access.
Zabbix proxy configuration.
Zabbix frontend configuration file.
Zabbix agent configuration.
Zabbix agent2 configuration.
version: '3.9'
services:
zabbix-server:
image: allworldit/zabbix:latest
hostname: zabbix-server
environment:
- ZABBIX_MODE=server
- ZABBIX_DATABASE_TYPE=timescaledb
- ZABBIX_ADMIN_USERNAME=Admin
- ZABBIX_ADMIN_PASSWORD=testtest
- ZABBIX_SERVER_WEBSERVICE_URL=http://zabbix-webservice:10053/report
- POSTGRES_HOST=postgresql
- POSTGRES_DATABASE=zabbix
- POSTGRES_USER=zabbix
- POSTGRES_PASSWORD=dbpassword
networks:
internal:
external:
ipv4_address: 172.16.10.10
ipv6_address: 64:ff9b:1::10:10
zabbix-frontend:
image: allworldit/zabbix:latest
environment:
ZABBIX_MODE: frontend
ZABBIX_DATABASE_TYPE: postgresql
POSTGRES_HOST: postgresql
POSTGRES_DATABASE: zabbix
POSTGRES_USER: zabbix
POSTGRES_PASSWORD: dbpassword
NGINX_SET_REAL_IP_FROM: |
172.16.0.0/12
64:ff9b:1::/96
ports:
- '8080:80'
networks:
internal:
external:
ipv4_address: 172.16.10.20
ipv6_address: 64:ff9b:1::10:20
zabbix-webservice:
image: allworldit/zabbix:latest
extra_hosts:
- "zabbix.frontend.example.com:172.16.0.1"
environment:
- ZABBIX_MODE=webservice
- ZABBIX_WEBSERVICE_ALLOWEDIP=zabbix-server
networks:
internal:
external:
ipv4_address: 172.16.10.30
ipv6_address: 64:ff9b:1::10:30
postgresql:
image: registry.conarx.tech/containers/postgresql-timescaledb
environment:
- POSTGRES_USER=zabbix
- POSTGRES_PASSWORD=dbpassword
- POSTGRES_DATABASE=zabbix
volumes:
- './data/postgresql:/var/lib/postgresql/data'
networks:
- internal
networks:
internal:
driver: bridge
enable_ipv6: true
internal: true
external:
driver: bridge
enable_ipv6: true
driver_opts:
com.docker.network.bridge.name: docker1
com.docker.network.enable_ipv6: 'true'
ipam:
driver: default
config:
- subnet: 172.16.10.0/24
- subnet: 64:ff9b:1::10:0/112
Content type
Image
Digest
sha256:2f82cc784…
Size
422.6 MB
Last updated
12 days ago
docker pull allworldit/zabbix