zabbix-server-pgsql-fips

Chainguard Container for zabbix-server-pgsql-fips

Minimalist Wolfi-based Zabbix FIPS images for centralized enterprise monitoring.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/zabbix-server-pgsql-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

FIPS Support

These images ship with a validated redistribution of OpenSSL's FIPS provider module, making them suitable for use in environments that require FIPS compliance. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

For non-FIPS deployments, see the standard zabbix image group.

Compatibility Notes

Chainguard's Zabbix FIPS images are designed as drop-in replacements for the official zabbix-docker images.

What's the same as upstream:

• User/Group IDs (UID 1997, GID 1995) - identical to official images
• Entrypoint scripts (/usr/bin/docker-entrypoint.sh) and behavior
• All standard environment variables (DB_SERVER_HOST, POSTGRES_*, ZBX_*, etc.)
• Directory paths (/etc/zabbix, /var/lib/zabbix, /usr/share/zabbix)
• Default ports (10051 for server/proxy, 8080 for web)
• Configuration file locations and formats

Differences from upstream:

Database Support: Chainguard currently provides PostgreSQL-backed server images and SQLite3-backed proxy images. If you require MySQL support, contact Chainguard for availability.

Minimal Images: Production images do not include a shell or package manager. For debugging, use the -dev variants or mount a debug container.

Available Images

The Zabbix FIPS image group consists of multiple container images:

For agent monitoring, use the separate zabbix-agent2-fips image.

Getting Started

Using Docker Compose

The following is a minimal Docker Compose example deploying Zabbix Server, Web UI, and PostgreSQL:

version: '3.8'
services:
  postgres:
    image: cgr.dev/ORGANIZATION/postgresql-fips:latest
    environment:
      POSTGRES_USER: zabbix
      POSTGRES_PASSWORD: zabbix
      POSTGRES_DB: zabbix
    volumes:
      - postgres_data:/var/lib/postgresql/data

  zabbix-server:
    image: cgr.dev/ORGANIZATION/zabbix-server-pgsql-fips:latest
    environment:
      DB_SERVER_HOST: postgres
      POSTGRES_USER: zabbix
      POSTGRES_PASSWORD: zabbix
      POSTGRES_DB: zabbix
    ports:
      - "10051:10051"
    depends_on:
      - postgres

  zabbix-web:
    image: cgr.dev/ORGANIZATION/zabbix-web-nginx-pgsql-fips:latest
    environment:
      DB_SERVER_HOST: postgres
      POSTGRES_USER: zabbix
      POSTGRES_PASSWORD: zabbix
      POSTGRES_DB: zabbix
      ZBX_SERVER_HOST: zabbix-server
      PHP_TZ: UTC
    ports:
      - "8080:8080"
    depends_on:
      - zabbix-server

volumes:
  postgres_data:

After starting the services, access the Zabbix web interface at http://localhost:8080 with the default credentials:

• Username: Admin
• Password: zabbix

Using Helm (Kubernetes)

For Kubernetes deployments, use the zabbix-community Helm chart:

helm repo add zabbix-community https://zabbix-community.github.io/helm-zabbix/
helm repo update

Install with Chainguard FIPS images:

helm install zabbix zabbix-community/zabbix \
  --namespace zabbix \
  --create-namespace \
  --set zabbixServer.image.repository=cgr.dev/ORGANIZATION/zabbix-server-pgsql-fips \
  --set zabbixServer.image.tag=latest \
  --set zabbixProxy.image.repository=cgr.dev/ORGANIZATION/zabbix-proxy-sqlite3-fips \
  --set zabbixProxy.image.tag=latest \
  --set zabbixWeb.image.repository=cgr.dev/ORGANIZATION/zabbix-web-nginx-pgsql-fips \
  --set zabbixWeb.image.tag=latest \
  --set zabbixAgent.image.repository=cgr.dev/ORGANIZATION/zabbix-agent2-fips \
  --set zabbixAgent.image.tag=latest

Be sure to replace ORGANIZATION with your organization's name in the Chainguard registry.

Environment Variables

The images support the same environment variables as the official Zabbix Docker images. Common variables include:

Server/Proxy:

• DB_SERVER_HOST - Database server hostname
• POSTGRES_USER - Database username
• POSTGRES_PASSWORD - Database password
• POSTGRES_DB - Database name
• ZBX_CACHESIZE - Configuration cache size
• ZBX_STARTPOLLERS - Number of pre-forked poller instances

Web Frontend:

• ZBX_SERVER_HOST - Zabbix Server hostname
• PHP_TZ - PHP timezone setting
• ZBX_SERVER_PORT - Zabbix Server port (default: 10051)

For a complete list of environment variables, refer to the official Zabbix Docker documentation.

Documentation and Resources

• Official Zabbix Documentation
• Zabbix Docker GitHub Repository
• Zabbix Community Helm Chart

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.