epicmorg/zabbix-server-pgsql repository overview

⁠EpicMorg Zabbix images

Every component of the official Zabbix⁠ container images, rebuilt on top of the upstream zabbix/<component>:<version>-ubuntu-latest tags with a few additions for day-to-day administration. The Zabbix software itself, its entrypoints and all configuration variables are unchanged - this README lists only what we add.

Version tags follow the upstream release lines (3.0 ... 7.4); latest follows upstream ubuntu-latest, trunk follows upstream ubuntu-trunk (development builds).

⁠What's inside

On top of the upstream image:

• apt sources replaced with full Ubuntu repositories (main restricted universe multiverse) for the Ubuntu release of that line;
• admin / troubleshooting tools: curl, wget, jq, nmap, telnet, iputils-ping, iperf / iperf3, iftop, iotop, htop, lsof, procps, smbclient, lynx, mc, nano, tmux, dos2unix, logrotate, acl, openssl, php-cli + php-curl (for PHP-based external checks and alert scripts);
• sudo for nmap: the zabbix user may run /usr/bin/nmap via sudo without a password (/etc/sudoers.d/zabbix) - for scans that need raw sockets;
• locales en_US, en_GB, ru_RU, ru_UA (UTF-8 plus legacy 8-bit charsets) and console-cyrillic;
• extra CA certificates in the system trust store: EpicMorg root / intermediate CAs and the Russian Trusted Root / Sub CAs.

⁠Tags

⁠epicmorg/zabbix-agent

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-agent:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-agent2

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-agent2:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-java-gateway

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-java-gateway:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-proxy-mysql

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-proxy-mysql:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-proxy-sqlite3

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-proxy-sqlite3:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-server-mysql

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-server-mysql:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-server-pgsql

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-server-pgsql:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-snmptraps

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-snmptraps:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-web-apache-mysql

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-web-apache-mysql:<tag> on each) - same digest everywhere.

⁠epicmorg/zabbix-web-apache-pgsql

Every tag is pushed to docker.io, quay.io and ghcr.io (epicmorg/zabbix-web-apache-pgsql:<tag> on each) - same digest everywhere.

⁠Usage

The images are drop-in replacements for the upstream ones: same ports, volumes and environment variables. Swap the image name in your existing deployment, e.g.:

services:
  zabbix-server:
    image: epicmorg/zabbix-server-pgsql:7.0
    environment:
      DB_SERVER_HOST: postgres
      POSTGRES_USER: zabbix
      POSTGRES_PASSWORD: zabbix
    ports:
      - "10051:10051"

  zabbix-web:
    image: epicmorg/zabbix-web-apache-pgsql:7.0
    environment:
      ZBX_SERVER_HOST: zabbix-server
      DB_SERVER_HOST: postgres
      POSTGRES_USER: zabbix
      POSTGRES_PASSWORD: zabbix
    ports:
      - "8080:8080"

  zabbix-agent:
    image: epicmorg/zabbix-agent2:7.0
    environment:
      ZBX_SERVER_HOST: zabbix-server

For the full list of environment variables, ports and volumes of every component see the upstream documentation: Zabbix in Docker⁠ and zabbix/zabbix-docker⁠.

⁠Notes

• Keep the server, proxy, web and agent tags on the same release line.
• Runtime user: 7.0, 7.2, 7.4, latest and trunk switch back to the upstream zabbix user; the older lines (3.0 ... 6.4) are left as root after our additions.
• trunk is upstream's development branch - not for production.
• Old lines (3.0, 4.0, ...) are kept for existing installations; they get no new upstream fixes.

⁠Links

• Source: EpicMorg/docker⁠ - issues and PRs welcome
• Tags float and are rebuilt weekly; pin by digest for reproducible builds: Tags, pinning and updates⁠
• CHANGELOG⁠ - License: MIT