readystack/zabbix repository overview

⁠Zabbix

readystack/zabbix:7.4.16-CE-ubuntu24.04-r2

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/zabbix/recipe⁠
• Upstream source at this release's pinned commit (7.4.16): https://github.com/zabbix/zabbix/tree/b90dda2ec5983a92c9671550b5e32947cf241cd2⁠
• Product page: https://readystack.dev/products/zabbix⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/zabbix⁠
• Release history (JSON): https://readystack.dev/api/releases/zabbix⁠
• Defect record: https://readystack.dev/defects.html?product=zabbix⁠
• Today's scan: https://readystack.dev/products/zabbix#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=zabbix⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/zabbix/zabbix 7.4.16 (AGPL-3.0-only), built clean-room from official upstream source, with the source changes listed below by ReadyStack⁠.

⁠Who uses it and why

Who: IT operations teams who monitor networks, servers, virtual machines, applications and cloud services.

Why: Zabbix is an open-source distributed monitoring solution. It discovers devices, collects metrics with or without agents, detects problems, sends alerts, and shows the data in graphs, maps and dashboards.

Use case: An IT team looks after switches, servers and databases across several offices. Zabbix discovers the devices, applies ready-made templates to monitor them, raises a problem when a disk fills or a link drops, and notifies the on-call administrator, including for offices behind firewalls.

About the upstream project, written from its own description: https://github.com/zabbix/zabbix⁠ · https://www.zabbix.com/documentation/current/en/manual/introduction/about⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:6be5b237ce49c1bb255d53858c729e4f54e912220f67a569f3b36c1cb3ec6a7c on 2026-10-28.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/zabbix⁠
• ReadyStack release check — passed at release on 2026-10-27: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:6be5b237ce49c1bb255d53858c729e4f54e912220f67a569f3b36c1cb3ec6a7c; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/zabbix:7.4.16-CE-ubuntu24.04-r2.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (zabbix).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 7.4.16-CE-ubuntu24.04-r2 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/zabbix:7.4.16-CE-ubuntu24.04-r2

# ✗ unsupported (do not pull)
docker pull readystack/zabbix:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/zabbix:7.4.16-CE-ubuntu24.04-r2 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container running zabbix_server in the foreground as the non-root zabbix user: the Zabbix monitoring engine (pollers, trappers, triggers, alerting) built from source. It REQUIRES an external PostgreSQL database (13 or newer); on first start against an empty database the entrypoint loads the Zabbix schema and seed data into it. The Zabbix web frontend and its JSON-RPC API are NOT in this image: run a Zabbix frontend (PHP) against the same database to configure hosts and see data. No Zabbix agent runs in this container.

Secrets go in an env file that only you can read, not on the command line, and passwords that only set up the first start come out of it after setup. Create zabbix.env with install -m 600 /dev/null zabbix.env, then write these lines into it with an editor, with your own values (a value typed into a shell stays in its history). Docker reads each line as written: no quotes around a value, no spaces around =.

# The PostgreSQL user's password; needed at every start.
POSTGRES_PASSWORD=YOUR_PW

docker run -d --name zabbix-server -p 10051:10051 -e DB_SERVER_HOST=YOUR_PG_HOST -e POSTGRES_USER=zabbix --env-file ./zabbix.env -e POSTGRES_DB=zabbix readystack/zabbix:7.4.16-CE-ubuntu24.04-r2

zabbix.env holds the database password (POSTGRES_PASSWORD), which the server needs at every start; write it without quotes (docker reads the line literally).

⁠Source changes (AGPL)

This software is licensed under the GNU Affero General Public License, and the releases below are built from a modified copy of its source. Each line names a release, what ReadyStack changed and where the diff is published. From 2026-10-27 a release's diff carries every upstream file its build changes, the dependency manifests and lockfiles included, so its complete corresponding source is the upstream tag with that diff applied; the diff of an earlier release carries the source edits its line names, and the dependency files that release's build changed are in its release archive (vendored/). If you let users interact with the server over a network, AGPL-3.0 section 13 asks you to offer them its source; for a release from 2026-10-27 on, a link to its diff and the upstream tag does that.

• 7.4.16-CE-ubuntu24.04-r2 — include/version.h has its ZABBIX_REVISION placeholder replaced by the first ten characters of the upstream commit, the revision stamp upstream's own make dist writes into its release tarballs; full diff at https://readystack.dev/source/zabbix/7.4.16/zabbix-7.4.16-readystack.patch⁠
• 7.4.16-CE-ubuntu24.04-r1 — include/version.h has its ZABBIX_REVISION placeholder replaced by the first ten characters of the upstream commit, the revision stamp upstream's own make dist writes into its release tarballs; full diff at https://readystack.dev/source/zabbix/7.4.16/zabbix-7.4.16-readystack.patch⁠

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/zabbix⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:a076e237d9451ae3032a101d985d6009cc8e822ae5e7800d0f4c08442a32430a on 2026-10-27.

— ReadyStack · readystack.dev