From 3a3e9f68af03bad955583571f2b14ab5d1a9372d Mon Sep 17 00:00:00 2001 From: Alexey Pustovalov Date: Fri, 15 Dec 2023 21:56:18 +0900 Subject: [PATCH] Updated information about report issues and rootless environments fping usage --- Dockerfiles/proxy-mysql/README.md | 10 ++++++++++ Dockerfiles/proxy-sqlite3/README.md | 10 ++++++++++ Dockerfiles/server-mysql/README.md | 10 ++++++++++ Dockerfiles/server-pgsql/README.md | 10 ++++++++++ README.md | 10 ++++++++-- 5 files changed, 48 insertions(+), 2 deletions(-) diff --git a/Dockerfiles/proxy-mysql/README.md b/Dockerfiles/proxy-mysql/README.md index 287d887cc3..8bea68bbbd 100644 --- a/Dockerfiles/proxy-mysql/README.md +++ b/Dockerfiles/proxy-mysql/README.md @@ -46,6 +46,16 @@ Start a Zabbix proxy container as follows: Where `some-zabbix-proxy-mysql` is the name you want to assign to your container, `some-mysql-server` is IP or DNS name of MySQL server, `some-user` is user to connect to Zabbix database on MySQL server, `some-password` is the password to connect to MySQL server, `some-hostname` is the hostname, it is Hostname parameter in Zabbix proxy configuration file, `some-zabbix-server` is IP or DNS name of Zabbix server and `tag` is the tag specifying the version you want. See the list above for relevant tags, or look at the [full list of tags](https://hub.docker.com/r/zabbix/zabbix-proxy-mysql/tags/). +> [!NOTE] +> Zabbix server has possibility to execute `fping` utility to perform ICMP checks. When containers are running in rootless mode or with specific restrictions environment, you may face errors related to fping: +> `fping: Operation not permitted` +> or +> lost all packets to all resources +> in this case add `--cap-add=net_raw` to `docker run` or `podman run` commands. +> Additionally fping executing in non-root environments can require sysctl modification: +> `net.ipv4.ping_group_range=0 1995` +> where 1995 is `zabbix` GID. + ## Connects from Zabbix server (Passive proxy) This image exposes the standard Zabbix proxy port (10051) and can operate as Passive proxy in case `ZBX_PROXYMODE` = `1`. Start Zabbix server container like this in order to link it to the Zabbix proxy container: diff --git a/Dockerfiles/proxy-sqlite3/README.md b/Dockerfiles/proxy-sqlite3/README.md index b070dc5887..454fc17da2 100644 --- a/Dockerfiles/proxy-sqlite3/README.md +++ b/Dockerfiles/proxy-sqlite3/README.md @@ -42,6 +42,16 @@ Start a Zabbix proxy container as follows: Where `some-zabbix-proxy-sqlite3` is the name you want to assign to your container, `some-hostname` is the hostname, it is Hostname parameter in Zabbix proxy configuration file, `some-zabbix-server` is IP or DNS name of Zabbix server and `tag` is the tag specifying the version you want. See the list above for relevant tags, or look at the [full list of tags](https://hub.docker.com/r/zabbix/zabbix-proxy-sqlite3/tags/). +> [!NOTE] +> Zabbix server has possibility to execute `fping` utility to perform ICMP checks. When containers are running in rootless mode or with specific restrictions environment, you may face errors related to fping: +> `fping: Operation not permitted` +> or +> lost all packets to all resources +> in this case add `--cap-add=net_raw` to `docker run` or `podman run` commands. +> Additionally fping executing in non-root environments can require sysctl modification: +> `net.ipv4.ping_group_range=0 1995` +> where 1995 is `zabbix` GID. + ## Connects from Zabbix server (Passive proxy) This image exposes the standard Zabbix proxy port (10051) and can operate as Passive proxy in case `ZBX_PROXYMODE` = `1`. Start Zabbix server container like this in order to link it to the Zabbix proxy container: diff --git a/Dockerfiles/server-mysql/README.md b/Dockerfiles/server-mysql/README.md index 2e59c869ac..0aab1fb8dc 100644 --- a/Dockerfiles/server-mysql/README.md +++ b/Dockerfiles/server-mysql/README.md @@ -48,6 +48,16 @@ Start a Zabbix server container as follows: Where `some-zabbix-server-mysql` is the name you want to assign to your container, `some-mysql-server` is IP or DNS name of MySQL server, `some-user` is user to connect to Zabbix database on MySQL server, `some-password` is the password to connect to MySQL server and `tag` is the tag specifying the version you want. See the list above for relevant tags, or look at the [full list of tags](https://hub.docker.com/r/zabbix/zabbix-server-mysql/tags/). +> [!NOTE] +> Zabbix server has possibility to execute `fping` utility to perform ICMP checks. When containers are running in rootless mode or with specific restrictions environment, you may face errors related to fping: +> `fping: Operation not permitted` +> or +> lost all packets to all resources +> in this case add `--cap-add=net_raw` to `docker run` or `podman run` commands. +> Additionally fping executing in non-root environments can require sysctl modification: +> `net.ipv4.ping_group_range=0 1995` +> where 1995 is `zabbix` GID. + ## Container shell access and viewing Zabbix server logs The `docker exec` command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your `zabbix-server-mysql` container: diff --git a/Dockerfiles/server-pgsql/README.md b/Dockerfiles/server-pgsql/README.md index 327f46261d..b2ddb1b4f2 100644 --- a/Dockerfiles/server-pgsql/README.md +++ b/Dockerfiles/server-pgsql/README.md @@ -47,6 +47,16 @@ Start a Zabbix server container as follows: Where `some-zabbix-server-pgsql` is the name you want to assign to your container, `some-postgres-server` is IP or DNS name of PostgreSQL server, `some-user` is user to connect to Zabbix database on PostgreSQL server, `some-password` is the password to connect to PostgreSQL server and `tag` is the tag specifying the version you want. See the list above for relevant tags, or look at the [full list of tags](https://hub.docker.com/r/zabbix/zabbix-server-pgsql/tags/). +> [!NOTE] +> Zabbix server has possibility to execute `fping` utility to perform ICMP checks. When containers are running in rootless mode or with specific restrictions environment, you may face errors related to fping: +> `fping: Operation not permitted` +> or +> lost all packets to all resources +> in this case add `--cap-add=net_raw` to `docker run` or `podman run` commands. +> Additionally fping executing in non-root environments can require sysctl modification: +> `net.ipv4.ping_group_range=0 1995` +> where 1995 is `zabbix` GID. + ## Container shell access and viewing Zabbix server logs The `docker exec` command allows you to run commands inside a Docker container. The following command line will give you a bash shell inside your `zabbix-server-pgsql` container: diff --git a/README.md b/README.md index 9d366d8577..1ff13064fc 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,8 @@ This repository contains **Dockerfile** of [Zabbix](https://zabbix.com/) for [Do * [oracle linux](https://hub.docker.com/_/oraclelinux/) from Zabbix 5.0 * [ubuntu](https://hub.docker.com/_/ubuntu/) -> **Important information: All Zabbix images based on CentOS 8 image can not be updated anymore because CentOS 8 base image is outdated on Docker Hub (base image is not updated for half year). CentOS Stream 8 from quay.io is used currently.** +> [!IMPORTANT] +> All Zabbix images based on CentOS 8 image can not be updated anymore because CentOS 8 base image is outdated on Docker Hub (base image is not updated for half year). CentOS Stream 8 and CentOS Stream 9 from quay.io is used currently.** ### Usage @@ -32,7 +33,9 @@ There is some documentation and examples in the [official Zabbix Documentation]( Please also follow usage instructions of each Zabbix component image: * [zabbix-appliance](https://hub.docker.com/r/zabbix/zabbix-appliance/) - Zabbix appliance with built-in MySQL server, Zabbix server, Zabbix Java Gateway and Zabbix frontend based on Nginx web-server - > **Important information: Zabbix Docker Appliance has been decommissioned and will not be available for 3.0.31, 4.0.19, 4.4.7, 5.0.0 and newer releases. Please use a separate Docker images for each component instead of the all-in-one solution.** + +> [!IMPORTANT] +> Zabbix Docker Appliance has been decommissioned and will not be available for 3.0.31, 4.0.19, 4.4.7, 5.0.0 and newer releases. Please use a separate Docker images for each component instead of the all-in-one solution.** * [zabbix-agent](https://hub.docker.com/r/zabbix/zabbix-agent/) - Zabbix agent * [zabbix-agent2](https://hub.docker.com/r/zabbix/zabbix-agent2/) - Zabbix agent 2 @@ -58,6 +61,9 @@ Templates support several [Compose profiles](https://docs.docker.com/compose/pr Be sure to check [the Wiki-page](https://github.com/zabbix/zabbix-docker/wiki) on common problems and questions. If you still have problems with or questions about the images, please contact us through a [GitHub issue](https://github.com/zabbix/zabbix-docker/issues). +> [!NOTE] +> Please report here issues and feature requests related to Docker images only. If you have issues or ideas how to improve Zabbix, use official [bug tracker](https://support.zabbix.com/). + ## Contributing You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.