VRx

New Update: - updated base image (alpine 3.14.1 -> 3.15) - updated webmin pkg (1.979 -> 1.984)

Sorry, I think I missed notification about reply. On the docker configuration page you have preconfigured /mnt/user and /mnt/cache (as array and cache pool). You can change it on Your own, for example by disk or maybe add some other pools. Access Mode can be just Read Only For example: /mnt/user on host You can bind to /mnt/array in zabbix agent container /mnt/cache on host You can bind to /mnt/something in zabbix agent container In Zabbix GUI You must set container paths to monitor, so: /mnt/array and /mnt/something

Check for container update and update it. Add new ENV: IPV6=enable Should work from now.

I haven't any, so i cannot test. But with your little help we could install some drivers and libs if it is not working.

It is ok. When You log in to GUI, You can simply create config. When You do that, bind process should start working. You do not need to create config manually before first run.

[Here] is beta plugin, should work like baremetal I think, but it is only agent not agent2, so it can't monitor docker containers.

You can run script on host and write output to file, which could be read by zabbix container. This is the easiest way. Most of templates are not prepared for zabbix-agent contenerized.

Ciągle o tym zapominałem. Poprawione + kilka innych baboli językowych. Ogólnie ktoś leciał chyba w ciemno translatorem, bez sprawdzania.

Update available: - fixed TZ env - fixed GUI_USER env

Yes You are right, but if someone have for example pihole container or something else what needs dns port... I can't know

find /mnt/user/surveillance_camera/cam[12] -type f -mtime +14 -delete find /mnt/user/surveillance_camera/cam[12] -type d -empty -delete

DNS requests mostly working on UDP, haproxy working on TCP.

Sed should do the same.

You can do this by logging in as root: docker exec -it --user=root zabbix-agent2 /bin/bash Next, edit group file (/etc/group) in vim or sed. If You not familiar with vim, sed will be easier: sed -i "s/docker:x:281:/docker:x:281:zabbix/g" /etc/group Next, type "exit" to exit container shell, then You can restart container from Unraid GUI BTW: Some trick could be used for things that not working from zabbix container, by setting up cron in User Scripts Plugin, this cron could monitor something, and write to file, which could be read by zabbix-agent, for example: my script read parameters from ups tools, writing output to file on cache pool, zabbix-agent read this file and parse output to different items in zabbix.

Because zabbix-agent2 in this container is running by the user without permissions to docker socket. There is a possibility to run this, but You must have basic knowledge about linux shell systems. You must check GID of docker group on Host (Unraid Server). Log in to zabbix-agent2 container as root user (default running "Console" from Unraid GUI made it but as zabbix user) Add group docker (with same gid as on host/unraid server) inside zabbix-agent2 container. Add user zabbix to this group. Restart zabbix-agent2 container. Note: You must do this again after every container update.

From now there will be weekly system update, every Sunday. But every changes in application, as always, will be reported in this thread.

TemplateURL is deprecated: You can simply ignore that error.

If You are using other DNS service, You could change network settings to custom bridge and assign other ip address for bind.

Update: - Fixed env variables (setting admin password should now work properly) - Fixed bind starting script (starting/restarting bind from webUI)

Yes You can. This change should resolve this problem. You cannot change port to 5353, because DNS Service is using port 53, and all operating systems are using this port to resolve hostnames by default. Maybe You have another service using this port, for example pihole container. Can You please post some error message, and some logs from this container or maybe send me PM with this informations as You prefer? There is a fix in progress, by the way of searching for solution, I found some other bugs.

@Owner did You have any error message? If You have error like attached below, this is not image problem. But known problem that sometimes pointing to /mnt/user is crashing. Let me know if message is different maybe.

It is working now. Thanks guys

I found another similar bug, array can't be stopped if Polish is active, but when switched to English, all working fine. In English there is a popup asking that I'm sure to stop array, or cancel parity checking, in Polish nothing is happend when I click the button.

I have added branches, so You can choose which version will be installed: default is 5.4 (latest stable) 5.0 4.4 Officially newer agent shoudn't work with older server.

Overview: Support for Docker template of the zabbix-agent container Application: Zabbix-Agent - https://www.zabbix.com/ DockerHub: https://hub.docker.com/r/zabbix/zabbix-agent https://hub.docker.com/r/zabbix/zabbix-agent2 Agent Version: newest stable Minimum Server Version: 6.9.2 Please use this support for unraid/docker issues/questions only. Zabbix have its own community forums, when You can find lots of information. Privileged mode does need to be left as enabled. This allows the agent to see system resources Adding Disks for Monitoring: On the docker configuration page you will preconfigured /mnt/user and /mnt/cache (as array and cache pool). You can change it on Your own, for example by disk or maybe add some other pools. Access Mode can be just Read Only Note, In Zabbix WebGUI You must set disk monitoring like Container Paths. * Please specify which version is affected by the problem (Agent or Agent2)