zabbix-docker: a version-named default branch, four documented base images and five in the Makefile
Official Zabbix Dockerfiles
At a glance
- What is it?
- The official Dockerfiles behind the Zabbix container images, with thirteen published component images and a Makefile that hides the real build complexity. The default pulls a moving latest tag rather than the versioned tags the project publishes, the documented base image list is one short of the Makefile's, and the licence moved from GPLv2 to AGPLv3 at version 7.0.
- Who is it for?
- zabbix-docker is the right starting point for a containerised Zabbix server because it is the vendor's own build definition, and the Makefile gives you a working stack with one command. Four things to know before you rely on it.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly Dockerfile, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- zabbix/zabbix-docker2,865 ★ · +18
| Repository | 2026-10-04 | 2026-11-15 |
|---|---|---|
| zabbix/zabbix-docker | 2.8k | 2.9k |
18 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The default branch is a version number, and two lines move in parallel
This repository's default branch is 7.4, not main or master, which tells you the branch structure is per release line. The tag list confirms it, with 7.4.15 published on 2026-09-23, 7.0.31 the day before, and 7.4.14 from a month earlier. Two lines are being maintained at once, and the newer one is the default, so a fresh clone is a working configuration for the current release and a stale configuration for an older supported one. The Makefile follows the same convention with a version variable that defaults to 7.4. The last push on that branch is dated 2026-09-24, and the repository is not archived. For anyone automating this, the practical consequence is that there is no single branch to track across versions: a deployment pinned to the 7.0 line needs a different checkout.
The README lists four base images and the Makefile defines five
The documentation names four base images: Alpine, CentOS, Oracle Linux and Ubuntu. The Makefile defines five variables, and the fifth is a Red Hat universal base image pointing at a versioned registry path. So a RHEL-based build is possible from this repository and is not documented in the image list. The defaults are also worth reading closely. Alpine is pinned to a release, CentOS to a stream tag with a minimal suffix, Oracle Linux to a version and a slim suffix, the RHEL image to a specific minor version. Ubuntu is the odd one out: its default is a codename tag rather than a numbered release, so the Ubuntu variant tracks whatever that codename currently resolves to. That is a deliberate trade for a smaller base image, and it is the one default in the file that can move without the Makefile changing.
The default image tag is a moving latest assembled from two variables
The Makefile separates what it pulls from what it builds. Remote images get a prefix and a tag assembled as the OS, the version and the literal word latest, so the default is a moving tag on Docker Hub rather than the versioned tag you tested. Locally built images get the same shape with local substituted for latest. The README states the same thing in prose: by default, Alpine based images and the latest version from the current branch are used. The consequence for a deployment is that rebuilding the stack on the same compose file can pick up a different image than the one you validated, while a versioned tag such as 7.4.15 is available if you pin it. There is a platform variable for multi-architecture builds, formatted as a comma separated list, so the same file covers an arm64 host when the local runtime supports it. The entry point is the Makefile, whose default goal is to bring the stack up, and whose documented commands are short:
make help
make up
make down DB=pgsqlOne compose file and four fragments, with the base OS carried in a label
The Compose story is split across five files in the root. The entry file pulls every service definition out of a components fragment using the extends key, which means the service shapes are declared once and reused. The database definitions live in another fragment, and a further fragment holds additional components, with a separate PostgreSQL variant of the entry file. Every service takes its image from a variable plus a shared tag variable, so switching database engine or web server is a matter of choosing which service the entry file extends and which variables are set. One detail does the work of letting the same file serve four operating systems: each service carries a label holding the OS variable, so the same compose file describes an Alpine stack and an Oracle Linux stack with the label recording which one is in play.
Each component gets its own database initialisation service
Ordering inside the stack is done with health conditions rather than a single migration step, and there is more than one initialisation job. The entry file defines a database init service for the server and another for the proxy, each extending a component from the fragments, each depending on the MySQL server being healthy, and each tagged with the same OS label. The server then depends on its own init service having completed successfully as well as on the database being healthy, and the MySQL-flavoured web front ends wait for the same init job rather than starting alongside it. The practical reading is that schema creation is per component, not global, so a deployment running only the proxy still gets its own initialisation, and a failure in one init service blocks exactly the services that need that schema instead of the whole stack.
The licence changed at version 7.0, with a request attached
The licence section is where the version branches get their consequence. From Zabbix version 7.0 onward, every subsequent release is published under the GNU Affero General Public License version 3, and you may modify and propagate a modified version under those terms. Every version up to 6.4 was under GPLv2. So a deployment that upgrades the 7.0 boundary moves from GPL to AGPL, and for anyone distributing a modified Zabbix inside a product that is the difference that matters. The section then adds a request rather than a condition: Zabbix is open source software, and users in a commercial context are asked to support development by purchasing some level of technical support. The repository's own licence file is AGPL-3.0, matching the current line.
Podman is a fallback, and issue routing splits images from the product
Two small mechanisms are worth knowing. The container runtime is auto-detected: the Makefile prefers Docker, falls back to Podman, and if neither exists it sets the variable to the word docker anyway so that help and variable printing still work on a machine with no runtime installed, with a comment saying the real targets will fail with an ordinary command not found error. You can override the choice yourself, for example by passing the container variable on the command line. Issue routing is split the same way: the README asks that image and Dockerfile issues and feature requests go to this repository, points at the project wiki for common problems, and sends anything about improving Zabbix itself to the vendor's own bug tracker. The repository also carries a Kubernetes manifest, a bake configuration for multi-platform builds, a committed environment file, and YAML linting wired into pre-commit.
Editorial conclusion
zabbix-docker is the right starting point for a containerised Zabbix server because it is the vendor's own build definition, and the Makefile gives you a working stack with one command. Four things to know before you rely on it. The default image tag is built as OS, version and latest, so a rebuild pulls whatever that tag points at rather than the versioned tag you tested. The base image list in the documentation is one shorter than the Makefile's, and the Ubuntu default is a codename tag rather than a version. Zabbix switched from GPLv2 to AGPLv3 at version 7.0, which matters if you redistribute. And issue routing is split: image problems go to this repository, product bugs go to the vendor's own tracker.
Frequently asked questions
What does the zabbix-docker repository contain?
The Dockerfiles for Zabbix used by the automated build that publishes images to the public Docker Hub registry, plus Compose files and a Makefile. Thirteen component images are published, including the agent, both server database variants, four web front end combinations across Apache and Nginx with MySQL or PostgreSQL, two proxies, the Java gateway, a headless web service for tasks such as reporting, and an SNMP trap container.
How do I start a Zabbix stack from the zabbix-docker repository?
Clone it, run make help, then run make up. The default uses Alpine based images and the latest version from the current branch. Variables customise it, for example make up DB=pgsql OS=alpine with the web ports set to 8282 and 8443, and make down DB=pgsql cleans up. It requires make and docker compose version 2.24.0 or greater.
Which base operating systems does zabbix-docker build for?
The README lists four, Alpine, CentOS, Oracle Linux and Ubuntu, while the Makefile defines five base image variables, adding a Red Hat universal base image. The defaults are alpine:3.24, a CentOS stream minimal tag, an Oracle Linux slim tag, ubuntu:resolute as a codename rather than a version, and a pinned universal base image minor version.
Can I use Podman instead of Docker with zabbix-docker?
Yes. The Makefile has a container variable that prefers Docker when it is available, falls back to Podman, and finally falls back to the string docker so help and variable printing still work without a runtime installed. You can also set it yourself, for example make CONTAINER=podman up.
Which image tag does zabbix-docker use by default?
Remote images are pulled with a tag assembled from the OS, the version and the word latest, so the default is a moving tag rather than a versioned one. Locally built images use the same shape with local in place of latest. The README confirms the default is Alpine based images and the latest version from the current branch.
What licence is Zabbix under from version 7.0?
From version 7.0 onward all Zabbix releases are published under the GNU Affero General Public License version 3, and modified versions may be propagated under those terms. All previous versions up to 6.4 were under GPLv2. The README also asks commercial users to support development by purchasing some level of technical support.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/zabbix-zabbix-docker)Star history chart for your README
[](https://hysenlabs.com/projects/zabbix-zabbix-docker)Was this useful?