In recent months I tried (at least a few times) and failed to upgrade my manually installed Ubuntu 18.04 / Zabbix 4.0 server so it makes sense to me that I should switch to installing and using Zabbix with Docker instead which should make upgrades easier/possible.
Using a docker compose file based upon the official Zabbix ubuntu/mysql compose seems like the best way for me to do this but I haven't quite got it working yet so I have a few questions which I hope will result in the existing Zabbix docker docs getting improved as a result. I am new to docker but I am familiar with LXD, LXC, proxmox, ansible, ZFS etc.
My first question is, is the Zabbix server ubuntu docker container known to work when run within an LXD (or LXC) container? Apparently some docker containers can be run under LXD whilst others have issues according to https://discourse.ubuntu.com/t/how-t...ntainers/26730 . I would like to run Zabbix via docker within an LXD container.
It would seem the (English) Zabbix docker compose docs are here:
https://www.zabbix.com/documentation...docker-compose
After having read that a couple of times, I have these questions.
It seems the absolute bare minimum you need to do to get Zabbix server running via docker compose is to edit your chosen compose file and remove all of the services you don't need so the first thing this guide is missing is a list of the minimum required services to set up a primary Zabbix server, something like this:
Required docker compose services for a primary Zabbix server with web interface:
zabbix-server
mysql-server OR postgres-server
zabbix-web-apache-mysql OR zabbix-web-nginx-mysql
I get the impression that zabbix-snmptraps and zabbix-web-service are optional for a standard Zabbix server install, if you're not monitoring SNMP. zabbix-java-gateway is only for those who wish to monitor compatible Java apps. It would be good if any optional services were noted as such in the comments for the compose files.
If the ONLY thing that the user does to configure their Zabbix server compose file is to edit out the services that they don't require, should they be able to login to the Zabbix server web interface immediately after running `docker compose up`? If this isn't going to work, then I think the docs should also include a list of the minimum environment variable that are required to be configured before running `compose up` so that the user is able to login to the web interface and begin setting things up, if its a new install, which brings me onto my next question.
After running `compose up`, what URL should I be trying to login to the Zabbix web interface with after it has been installed using docker containers? An example URL for the zabbix-server web admin interface should be added to the end of the compose section.
If we can answer all of those questions I think the docs be much more friendly to zabbix/docker beginners.
Thanks
Using a docker compose file based upon the official Zabbix ubuntu/mysql compose seems like the best way for me to do this but I haven't quite got it working yet so I have a few questions which I hope will result in the existing Zabbix docker docs getting improved as a result. I am new to docker but I am familiar with LXD, LXC, proxmox, ansible, ZFS etc.
My first question is, is the Zabbix server ubuntu docker container known to work when run within an LXD (or LXC) container? Apparently some docker containers can be run under LXD whilst others have issues according to https://discourse.ubuntu.com/t/how-t...ntainers/26730 . I would like to run Zabbix via docker within an LXD container.
It would seem the (English) Zabbix docker compose docs are here:
https://www.zabbix.com/documentation...docker-compose
After having read that a couple of times, I have these questions.
It seems the absolute bare minimum you need to do to get Zabbix server running via docker compose is to edit your chosen compose file and remove all of the services you don't need so the first thing this guide is missing is a list of the minimum required services to set up a primary Zabbix server, something like this:
Required docker compose services for a primary Zabbix server with web interface:
zabbix-server
mysql-server OR postgres-server
zabbix-web-apache-mysql OR zabbix-web-nginx-mysql
I get the impression that zabbix-snmptraps and zabbix-web-service are optional for a standard Zabbix server install, if you're not monitoring SNMP. zabbix-java-gateway is only for those who wish to monitor compatible Java apps. It would be good if any optional services were noted as such in the comments for the compose files.
If the ONLY thing that the user does to configure their Zabbix server compose file is to edit out the services that they don't require, should they be able to login to the Zabbix server web interface immediately after running `docker compose up`? If this isn't going to work, then I think the docs should also include a list of the minimum environment variable that are required to be configured before running `compose up` so that the user is able to login to the web interface and begin setting things up, if its a new install, which brings me onto my next question.
After running `compose up`, what URL should I be trying to login to the Zabbix web interface with after it has been installed using docker containers? An example URL for the zabbix-server web admin interface should be added to the end of the compose section.
If we can answer all of those questions I think the docs be much more friendly to zabbix/docker beginners.
Thanks