Docker Image with Zabbix server

[jan.garaj]

Docs:

https://github.com/veggiemonk/awesome-docker

Tutorial about building of Docker images https://www.digitalocean.com/communi...ding-of-images

Then is also good to know how to optimize images: https://github.com/veggiemonk/awesom...imizing-images

[polinux]

Hi,

I have made some changes and now we have a "master/base" image under million12/zabbix-server-base which is build from a Dockerfile in which you can specify any version of Zabbix based on tag number.

Tag on Docker Hub corresponds with Zabbix tag version. For now there is latest version tagged with 2.4.5

Later on I will add some automation into this process as Jan pointed out. For now I have to focus on few different tasks. But feel free to work on it and send PR with changes.

PS. Jan if you have more ideas I'm all ears.

[jan.garaj]

Is it possible to:
- rename final image zabbix-server-2.4 (it will provide space for LTS 2.2 and unstable-trunk versions)
- create full history layers: now is only 2.4.5, I recommend to start 2.4.0 and then add every releases (rc included) and latest will be 2.4.5, it can help to people with older releases

I'll try to investigate build options (github webhook/drone.io/docker registry)

[polinux]

Is it possible to:
- rename final image zabbix-server-2.4 (it will provide space for LTS 2.2 and unstable-trunk versions)
- create full history layers: now is only 2.4.5, I recommend to start 2.4.0 and then add every releases (rc included) and latest will be 2.4.5, it can help to people with older releases

I'll try to investigate build options (github webhook/drone.io/docker registry)

OK Done. It's available under name million12/zabbix-server.2.4 and all versions are building now. It might take a while until finished but all subversions are added already.
All versions are running CircleCI tests as well to make sure they all work.
Branch in GitHub named 2.4 corresponds to this image.

PS. Any more ideas?

[jan.garaj]

Building/committing of layers https://docs.docker.com/userguide/do...tting-an-image Unfortunately I don't have handsome experience with this type of building.

Maybe http://docs.docker.com/docker-hub/builds/ supports also building by layers, if you setup also github tags + docker tags, but I'm not sure.

Probably some scripting will be needed.

[polinux]

Building/committing of layers https://docs.docker.com/userguide/do...tting-an-image Unfortunately I don't have handsome experience with this type of building.

Maybe http://docs.docker.com/docker-hub/builds/ supports also building by layers, if you setup also github tags + docker tags, but I'm not sure.

Probably some scripting will be needed.

I think for time being we are set ok. Tags in Docker Hub and GitHub match each other so when next version is released I'll add it on GitHub and start new build in Docker Hub based on that tag.

For now we have all 2.4.x versions build.

[jan.garaj]

Perfect, the best docker image of zabbix-server on docker market.

If you (and zabbix community authorities) don't mind, then I would like to move base version to:
1.) github.com/zabbix/zabbix-docker - repo for Dockerfiles; now for zabbix-server project, but also for zabbix-agent, zabbix-proxy, zabbix-web?(+LTS version 2.2 + unstable-trunk version) in future
2.) registry.hub.docker.com/repos/zabbix/ - automated build(s) for zabbix-server-mysql-2.4 (if it's possible to compile full DB support, then it can be only zabbix-server)

It should probably mimic current zabbix rpm packages conventions and on the top of base zabbix images can anyone build/provide own functionality (for example your custom image with slack, smtp script, ...)

[polinux]

Im fine with that.

Let me know when to transfer the ownership and to whom.

PS. By full DB support you mean having mysql DB running inside that docker image or you want to have it compiled with support for lets say PostgreSQL?