[ZBX-18420] Docker based Zabbix-Agent: Cannot ping/access Docker Daemon from within docker Created: 2020 Sep 27 Updated: 2020 Sep 28 Resolved: 2020 Sep 27 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G) |
Affects Version/s: | 5.0.3 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | Max Michaels | Assignee: | Zabbix Support Team |
Resolution: | Won't fix | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
CentOS 7 Docker host |
Description |
Steps to reproduce:
I am stumped as to what I need to do in order to give the Zabbix Agent proper access to the Docker Daemon it is running on. On the host outside the container I can "ping docker-host" just fine but within the zabbix-agent container it fails... Result:
|
Comments |
Comment by Edgar Akhmetshin [ 2020 Sep 27 ] |
Docker has different type of network options: https://docs.docker.com/network/, connectivity issue is not related to the Zabbix. May be you have bridge network, so you need to monitor address of the container behind bridge or expose correctly ports for the Agent container. Please note - to monitor Docker you need to mount volume with Docker socket path to the Agent container. Also you need to use Agent 2 (GO written). https://www.zabbix.com/documentation/current/manual/config/templates_out_of_the_box/zabbix_agent2 Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support or consultancy services. Alternatively, you can also use our IRC channel or community forum (https://www.zabbix.com/forum) for assistance. With that said, we are closing this ticket. Thank you for understanding. |