extern/zabbix-docker
1
0
Fork 0
mirror of https://github.com/zabbix/zabbix-docker.git synced 2025-07-16 06:25:22 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated FAQnP ... Frequently asked questions and problems (markdown)

Markus Fischbacher
2021-03-18 10:35:00 +01:00
parent 840242e7ee
commit ec87bbab1c
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
FAQnP-...-Frequently-asked-questions-and-problems.md

@ -1,5 +1,10 @@
## all containers running but "Zabbix server" host item not reachable in UI
Thats because the default "Zabbix server" item in Zabbix is looking for "localhost" which isn't working in containers as it's normal.
So to solve that problem you can:
- simple change "localhost" to "zabbix-agent" which points to the, hopefully also started, Zabbix Agent container.
- or, arguably better!, you remove the Zabbix Agent template from "Zabbix server" (while leaving the Zabbix server templates!) and create a new host "Zabbix agent" which you point to the zabbix-agent container and link the template there.
- or, arguably better!, you remove the Zabbix Agent template from "Zabbix server" (while leaving the Zabbix server templates!) and create a new host "Zabbix agent" which you point to the zabbix-agent container and link the template there.
## why are there so many containers with Docker Compose?
Because there are so many possible configuration combinations there are also a lot of docker-compose templates. The highlight here is on templates! They simply aren't supposed to be `docker-compose up -d -f docker-compose_v3_ubuntu_pgsql_latest.yaml`. You should instead copy the one you like and then tailor it to your needs. So for example if you choose Postgres as your DB copy the pgsql_latest to docker-compose.yml and just keep the services you need.