extern/zabbix-docker
1
0
Fork 0
mirror of https://github.com/zabbix/zabbix-docker.git synced 2025-08-26 23:54:00 +02:00
Code Issues Packages Projects Releases Wiki Activity

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

Waldek Maleska
2023-02-08 09:29:09 +00:00
parent b3409a500a
commit 3a0b2a74f8
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -5,6 +5,7 @@ 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.
- argument against: this solution seems cleaner but the problem is, zabbix-agent is no longer part of the same Docker network and the DNS name is no longer resolvable. At the same time, Agent requires server's DNS or IP address in its config file (`Server` and `ServerActive` options) and because that IP address is not known up front - it's not possible to establish a successful connection.
## 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.