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

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

Markus Fischbacher
2021-03-18 14:38:57 +01:00
parent ec87bbab1c
commit 556c7545e3
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -7,4 +7,12 @@ So to solve that problem you can:
- 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? ## 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. 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.
## The agent container states "host [xxx] not found"
```log
22264:20210318:123205.124 no active checks on server [zabbix-server:10051]: host [722372e65167] not found
```
Every time a container is created it gets a new id/hostname unless you set the `hostname: zabbix-agent` or add `ZBX_HOSTNAME=zabbix-agent` to the env variables. Then you can create an Zabbix host with `zabbix-agent` as item.