Fixed variable descriptions

Dockerfiles/agent/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix agent?</h2>
 <p>Zabbix agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc).</p>
 <h2>Zabbix agent images</h2>
@@ -138,13 +138,3 @@ ZBX_ALLOWKEY= # Available since 5.0.0
 <p>The volume allows load additional modules and extend Zabbix agent using <code>LoadModule</code> feature.</p>
 <h4><code>/var/lib/zabbix/enc</code></h4>
 <p>The volume is used to store TLS related files. These file names are specified using <code>ZBX_TLSCAFILE</code>, <code>ZBX_TLSCRLFILE</code>, <code>ZBX_TLSCERTFILE</code>, <code>ZBX_TLSKEYFILE</code> and <code>ZBX_TLSPSKFILE</code> variables. Additionally it is possible to use environment variables <code>ZBX_TLSCA</code>, <code>ZBX_TLSCRL</code>, <code>ZBX_TLSCERT</code>, <code>ZBX_TLSKEY</code> and <code>ZBX_TLSPSK</code> with plaintext values.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/agent"><code>agent/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<p>Currently it is not allowed to specify <code>ZBX_ALIAS</code> environment variable. Please use <code>/etc/zabbix/zabbix_agentd.d</code> volume with additional configuration files with <code>Alias</code> options.</p>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/agent2/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix agent 2?</h2>
 <p>Zabbix agent 2 is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc).</p>
 <h2>Zabbix agent 2 images</h2>
@@ -140,13 +140,3 @@ ZBX_ALLOWKEY= # Available since 5.0.0
 <p>The volume is used to store TLS related files. These file names are specified using <code>ZBX_TLSCAFILE</code>, <code>ZBX_TLSCRLFILE</code>, <code>ZBX_TLSCERTFILE</code>, <code>ZBX_TLSKEYFILE</code> and <code>ZBX_TLSPSKFILE</code> variables. Additionally it is possible to use environment variables <code>ZBX_TLSCA</code>, <code>ZBX_TLSCRL</code>, <code>ZBX_TLSCERT</code>, <code>ZBX_TLSKEY</code> and <code>ZBX_TLSPSK</code> with plaintext values.</p>
 <h4><code>/var/lib/zabbix/buffer</code></h4>
 <p>The volume is used to store the file, where Zabbix Agent2 should keep SQLite database. To enable the feature specify <code>ZBX_ENABLEPERSISTENTBUFFER=true</code>. Available since 5.0.0.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/agent2"><code>agent2/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<p>Currently it is not allowed to specify <code>ZBX_ALIAS</code> environment variable. Please use <code>/etc/zabbix/zabbix_agentd.d</code> volume with additional configuration files with <code>Alias</code> options.</p>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/java-gateway/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix Java Gateway?</h2>
 <p>Zabbix Java Gateway performs native support for monitoring JMX applications. Java gateway accepts incoming connection from Zabbix server or Zabbix proxy and can only be used as a "passive proxy".</p>
 <h2>Zabbix Java Gateway images</h2>
@@ -42,12 +42,3 @@
 <h3>Allowed volumes for the Zabbix Java Gateway container</h3>
 <h4><code>/usr/sbin/zabbix_java/ext_lib</code></h4>
 <p>The volume allows include additional JAR files to extend allowed protocols for Zabbix Java Gateway.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/java-gateway"><code>java-gateway/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/proxy-mysql/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix proxy?</h2>
 <p>Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.</p>
 <h2>Zabbix proxy images</h2>
@@ -33,7 +33,7 @@ Zabbix server has possibility to execute <code>fping</code> utility to perform I
 <code>fping: Operation not permitted</code>
 or
 lost all packets to all resources
-in this case add <code>--cap-add=net_raw</code> to <code>docker run</code> or <code>podman run</code> commands.
+in this case add <code>--cap-add=net_raw</code> to <code>podman run</code> commands.
 Additionally fping executing in non-root environments can require sysctl modification:
 <code>net.ipv4.ping_group_range=0 1995</code>
 where 1995 is <code>zabbix</code> GID.</p>
@@ -74,7 +74,7 @@ where 1995 is <code>zabbix</code> GID.</p>
 <h4><code>DB_SERVER_PORT</code></h4>
 <p>This variable is port of MySQL server. By default, value is '3306'.</p>
 <h4><code>MYSQL_USER</code>, <code>MYSQL_PASSWORD</code>, <code>MYSQL_USER_FILE</code>, <code>MYSQL_PASSWORD_FILE</code></h4>
-<p>These variables are used by Zabbix proxy to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. Without Docker Swarm or Kubernetes you also have to map the files. Those are exclusive so you can just provide one type - either <code>MYSQL_USER</code> or <code>MYSQL_USER_FILE</code>!</p>
+<p>These variables are used by Zabbix proxy to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. When secrets are not managed by an orchestrator, you also have to mount the files. Those are exclusive so you can just provide one type - either <code>MYSQL_USER</code> or <code>MYSQL_USER_FILE</code>!</p>
 <pre><code>podman run \
     --name some-zabbix-proxy-mysql \
     -e DB_SERVER_HOST=&quot;some-mysql-server&quot; \
@@ -87,7 +87,7 @@ where 1995 is <code>zabbix</code> GID.</p>
     --init \
     -d registry.connect.redhat.com/zabbix/zabbix-proxy-mysql-74:tag
 </code></pre>
-<p>With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!</p>
+<p>Podman secrets can be used to avoid exposing credentials in the command line:</p>
 <pre><code>printf &quot;zabbix&quot; | podman secret create MYSQL_USER -
 printf &quot;zabbix&quot; | podman secret create MYSQL_PASSWORD -
 podman run \
@@ -230,12 +230,3 @@ ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
 SNMP traps processing feature could be enabled using shared volume and switched <code>ZBX_ENABLE_SNMP_TRAPS</code> environment variable to <code>true</code>.</p>
 <h4><code>/var/lib/zabbix/mibs</code></h4>
 <p>The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in <code>/var/lib/zabbix/mibs</code>.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/proxy-mysql"><code>proxy-mysql/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/proxy-sqlite3/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix proxy?</h2>
 <p>Zabbix proxy is a process that may collect monitoring data from one or more monitored devices and send the information to the Zabbix server, essentially working on behalf of the server. All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to.</p>
 <h2>Zabbix proxy images</h2>
@@ -24,7 +24,7 @@ Zabbix server has possibility to execute <code>fping</code> utility to perform I
 <code>fping: Operation not permitted</code>
 or
 lost all packets to all resources
-in this case add <code>--cap-add=net_raw</code> to <code>docker run</code> or <code>podman run</code> commands.
+in this case add <code>--cap-add=net_raw</code> to <code>podman run</code> commands.
 Additionally fping executing in non-root environments can require sysctl modification:
 <code>net.ipv4.ping_group_range=0 1995</code>
 where 1995 is <code>zabbix</code> GID.</p>
@@ -174,12 +174,3 @@ ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
 SNMP traps processing feature could be enabled using shared volume and switched <code>ZBX_ENABLE_SNMP_TRAPS</code> environment variable to <code>true</code>.</p>
 <h4><code>/var/lib/zabbix/mibs</code></h4>
 <p>The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in <code>/var/lib/zabbix/mibs</code>.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/proxy-sqlite3"><code>proxy-sqlite3/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/server-mysql/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix server?</h2>
 <p>Zabbix server is the central process of Zabbix software.</p>
 <p>The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.</p>
@@ -32,7 +32,7 @@ Zabbix server has possibility to execute <code>fping</code> utility to perform I
 <code>fping: Operation not permitted</code>
 or
 lost all packets to all resources
-in this case add <code>--cap-add=net_raw</code> to <code>docker run</code> or <code>podman run</code> commands.
+in this case add <code>--cap-add=net_raw</code> to <code>podman run</code> commands.
 Additionally fping executing in non-root environments can require sysctl modification:
 <code>net.ipv4.ping_group_range=0 1995</code>
 where 1995 is <code>zabbix</code> GID.</p>
@@ -51,7 +51,7 @@ where 1995 is <code>zabbix</code> GID.</p>
 <h4><code>DB_SERVER_PORT</code></h4>
 <p>This variable is port of MySQL server. By default, value is '3306'.</p>
 <h4><code>MYSQL_USER</code>, <code>MYSQL_PASSWORD</code>, <code>MYSQL_USER_FILE</code>, <code>MYSQL_PASSWORD_FILE</code></h4>
-<p>These variables are used by Zabbix server to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. Without Docker Swarm or Kubernetes you also have to map the files. Those are exclusive so you can just provide one type - either <code>MYSQL_USER</code> or <code>MYSQL_USER_FILE</code>!</p>
+<p>These variables are used by Zabbix server to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. When secrets are not managed by an orchestrator, you also have to mount the files. Those are exclusive so you can just provide one type - either <code>MYSQL_USER</code> or <code>MYSQL_USER_FILE</code>!</p>
 <pre><code>podman run \
     --name some-zabbix-server-mysql \
     -e DB_SERVER_HOST=&quot;some-mysql-server&quot; \
@@ -62,7 +62,7 @@ where 1995 is <code>zabbix</code> GID.</p>
     --init \
     -d registry.connect.redhat.com/zabbix/zabbix-server-mysql-74:tag
 </code></pre>
-<p>With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!</p>
+<p>Podman secrets can be used to avoid exposing credentials in the command line:</p>
 <pre><code>printf &quot;zabbix&quot; | podman secret create MYSQL_USER -
 printf &quot;zabbix&quot; | podman secret create MYSQL_PASSWORD -
 podman run \
@@ -225,12 +225,3 @@ SNMP traps processing feature could be enabled using shared volume and switched
 <p>The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in <code>/var/lib/zabbix/mibs</code>.</p>
 <h4><code>/var/lib/zabbix/export</code></h4>
 <p>Directory for real-time export of events, history and trends in newline-delimited JSON format. Could be enabled using <code>ZBX_EXPORTFILESIZE</code> environment variable.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/server-mysql"><code>server-mysql/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/server-pgsql/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix server?</h2>
 <p>Zabbix server is the central process of Zabbix software.</p>
 <p>The server performs the polling and trapping of data, it calculates triggers, sends notifications to users. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. The server can itself remotely check networked services (such as web servers and mail servers) using simple service checks.</p>
@@ -31,7 +31,7 @@ Zabbix server has possibility to execute <code>fping</code> utility to perform I
 <code>fping: Operation not permitted</code>
 or
 lost all packets to all resources
-in this case add <code>--cap-add=net_raw</code> to <code>docker run</code> or <code>podman run</code> commands.
+in this case add <code>--cap-add=net_raw</code> to <code>podman run</code> commands.
 Additionally fping executing in non-root environments can require sysctl modification:
 <code>net.ipv4.ping_group_range=0 1995</code>
 where 1995 is <code>zabbix</code> GID.</p>
@@ -50,7 +50,7 @@ where 1995 is <code>zabbix</code> GID.</p>
 <h4><code>DB_SERVER_PORT</code></h4>
 <p>This variable is port of PostgreSQL server. By default, value is '5432'.</p>
 <h4><code>POSTGRES_USER</code>, <code>POSTGRES_PASSWORD</code>, <code>POSTGRES_USER_FILE</code>, <code>POSTGRES_PASSWORD_FILE</code></h4>
-<p>These variables are used by Zabbix server to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. Without Docker Swarm or Kubernetes you also have to map the files. Those are exclusive so you can just provide one type - either <code>POSTGRES_USER</code> or <code>POSTGRES_USER_FILE</code>!</p>
+<p>These variables are used by Zabbix server to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. When secrets are not managed by an orchestrator, you also have to mount the files. Those are exclusive so you can just provide one type - either <code>POSTGRES_USER</code> or <code>POSTGRES_USER_FILE</code>!</p>
 <pre><code>podman run \
     --name some-zabbix-server-pgsql \
     -e DB_SERVER_HOST=&quot;some-postgres-server&quot; \
@@ -61,7 +61,7 @@ where 1995 is <code>zabbix</code> GID.</p>
     --init \
     -d registry.connect.redhat.com/zabbix/zabbix-server-pgsql-74:tag
 </code></pre>
-<p>With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!</p>
+<p>Podman secrets can be used to avoid exposing credentials in the command line:</p>
 <pre><code>printf &quot;zabbix&quot; | podman secret create POSTGRES_USER -
 printf &quot;zabbix&quot; | podman secret create POSTGRES_PASSWORD -
 podman run \
@@ -225,13 +225,3 @@ SNMP traps processing feature could be enabled using shared volume and switched
 <p>The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in <code>/var/lib/zabbix/mibs</code>.</p>
 <h4><code>/var/lib/zabbix/export</code></h4>
 <p>Directory for real-time export of events, history and trends in newline-delimited JSON format. Could be enabled using <code>ZBX_EXPORTFILESIZE</code> environment variable.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/server-pgsql"><code>server-pgsql/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<p>Zabbix server does not support Jabber notifications on Alpine Linux because of <code>iksemel</code> package is in testing repository and not available in stable repository.</p>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/snmptraps/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is the image?</h2>
 <p>The image is used to receive SNMP traps, store them to a log file and provide access to Zabbix to collected SNMP trap messsages.</p>
 <h2>Zabbix snmptraps images</h2>
@@ -47,12 +47,3 @@
 <h4><code>/var/lib/zabbix/snmptrapd_config</code></h4>
 <p>The volume various persistent configuration files generated by snmptrapd daemon. The volume is required usually only for SNMPv3 traps. Do not modify manually anything stored in the volume.</p>
 <p>The volume also can be used for custom configuration file <code>snmptrapd_custom.conf</code>. The configuration file can be used for SNMPv3 authentification details.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/snmptraps"><code>snmptraps/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/web-nginx-mysql/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix web interface?</h2>
 <p>Zabbix web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics.</p>
 <h2>Zabbix web interface images</h2>
@@ -67,7 +67,7 @@
 <h4><code>DB_SERVER_PORT</code></h4>
 <p>This variable is port of MySQL server. By default, value is '3306'.</p>
 <h4><code>MYSQL_USER</code>, <code>MYSQL_PASSWORD</code>, <code>MYSQL_USER_FILE</code>, <code>MYSQL_PASSWORD_FILE</code></h4>
-<p>These variables are used by Zabbix web-interface to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. Without Docker Swarm or Kubernetes you also have to map the files. Those are exclusive so you can just provide one type - either <code>MYSQL_USER</code> or <code>MYSQL_USER_FILE</code>!</p>
+<p>These variables are used by Zabbix web-interface to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. When secrets are not managed by an orchestrator, you also have to mount the files. Those are exclusive so you can just provide one type - either <code>MYSQL_USER</code> or <code>MYSQL_USER_FILE</code>!</p>
 <pre><code>podman run \
     --name some-zabbix-web-nginx-mysql \
     -e DB_SERVER_HOST=&quot;some-mysql-server&quot; \
@@ -78,7 +78,7 @@
     -e PHP_TZ=&quot;some-timezone&quot; \
     -d registry.connect.redhat.com/zabbix/zabbix-web-mysql-74:tag
 </code></pre>
-<p>With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!</p>
+<p>Podman secrets can be used to avoid exposing credentials in the command line:</p>
 <pre><code>printf &quot;zabbix&quot; | podman secret create MYSQL_USER -
 printf &quot;zabbix&quot; | podman secret create MYSQL_PASSWORD -
 podman run \
@@ -150,7 +150,7 @@ podman run \
 <p>Example of YAML Mapping to Sequences</p>
 <pre><code>....
   environment:
-    ZBX_SSO_SETTINGS: &quot;{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}&quot;
+    ZBX_SSO_SETTINGS: &quot;{'baseurl': 'https://zabbix.example.com', 'use_proxy_headers': true, 'strict': false}&quot;
     ....
 ....
 </code></pre>
@@ -197,12 +197,3 @@ WEB_REAL_IP_HEADER=
 <p>The volume allows to use custom certificates for SAML authentication. The volume must contain three files <code>sp.key</code>, <code>sp.crt</code> and <code>idp.crt</code>. Available since 5.0.0.</p>
 <h4><code>/var/lib/zabbix/enc</code></h4>
 <p>The volume is used to store TLS related files. These file names are specified using <code>ZBX_SERVER_TLS_CAFILE</code>, <code>ZBX_SERVER_TLS_KEYFILE</code> and <code>ZBX_SERVER_TLS_CERTFILE</code> variables. Additionally it is possible to use environment variables <code>ZBX_SERVER_TLS_CA</code>, <code>ZBX_SERVER_TLS_KEY</code> and <code>ZBX_SERVER_TLS_CERT</code> with plaintext values. Available since 7.4.0.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/web-nginx-mysql"><code>web-nginx-mysql/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/web-nginx-pgsql/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix web interface?</h2>
 <p>Zabbix web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics.</p>
 <h2>Zabbix web interface images</h2>
@@ -67,7 +67,7 @@
 <h4><code>DB_SERVER_PORT</code></h4>
 <p>This variable is port of PostgreSQL server. By default, value is '5432'.</p>
 <h4><code>POSTGRES_USER</code>, <code>POSTGRES_PASSWORD</code>, <code>POSTGRES_USER_FILE</code>, <code>POSTGRES_PASSWORD_FILE</code></h4>
-<p>These variables are used by Zabbix web interface to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. Without Docker Swarm or Kubernetes you also have to map the files. Those are exclusive so you can just provide one type - either <code>POSTGRES_USER</code> or <code>POSTGRES_USER_FILE</code>!</p>
+<p>These variables are used by Zabbix web interface to connect to Zabbix database. With the <code>_FILE</code> variables you can instead provide the path to a file which contains the user / the password instead. When secrets are not managed by an orchestrator, you also have to mount the files. Those are exclusive so you can just provide one type - either <code>POSTGRES_USER</code> or <code>POSTGRES_USER_FILE</code>!</p>
 <pre><code>podman run \
     --name some-zabbix-web-nginx-pgsql \
     -e DB_SERVER_HOST=&quot;some-postgres-server&quot; \
@@ -79,7 +79,7 @@
     -e PHP_TZ=&quot;some-timezone&quot; \
     -d registry.connect.redhat.com/zabbix/zabbix-web-pgsql-74:tag
 </code></pre>
-<p>With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!</p>
+<p>Podman secrets can be used to avoid exposing credentials in the command line:</p>
 <pre><code>printf &quot;zabbix&quot; | podman secret create POSTGRES_USER -
 printf &quot;zabbix&quot; | podman secret create POSTGRES_PASSWORD -
 podman run \
@@ -151,7 +151,7 @@ podman run \
 <p>Example of YAML Mapping to Sequences</p>
 <pre><code>....
   environment:
-    ZBX_SSO_SETTINGS: &quot;{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}&quot;
+    ZBX_SSO_SETTINGS: &quot;{'baseurl': 'https://zabbix.example.com', 'use_proxy_headers': true, 'strict': false}&quot;
     ....
 ....
 </code></pre>
@@ -198,12 +198,3 @@ WEB_REAL_IP_HEADER=
 <p>The volume allows to use custom certificates for SAML authentication. The volume must contain three files <code>sp.key</code>, <code>sp.crt</code> and <code>idp.crt</code>. Available since 5.0.0.</p>
 <h4><code>/var/lib/zabbix/enc</code></h4>
 <p>The volume is used to store TLS related files. These file names are specified using <code>ZBX_SERVER_TLS_CAFILE</code>, <code>ZBX_SERVER_TLS_KEYFILE</code> and <code>ZBX_SERVER_TLS_CERTFILE</code> variables. Additionally it is possible to use environment variables <code>ZBX_SERVER_TLS_CA</code>, <code>ZBX_SERVER_TLS_KEY</code> and <code>ZBX_SERVER_TLS_CERT</code> with plaintext values. Available since 7.4.0.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/web-nginx-pgsql"><code>web-nginx-pgsql/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>

Dockerfiles/web-service/rhel/README.html

@@ -1,7 +1,7 @@
 <h2>What is Zabbix?</h2>
 <p>Zabbix is an enterprise-class open source distributed monitoring solution.</p>
 <p>Zabbix is software that monitors numerous parameters of a network and the health and integrity of servers. Zabbix uses a flexible notification mechanism that allows users to configure e-mail based alerts for virtually any event. This allows a fast reaction to server problems. Zabbix offers excellent reporting and data visualisation features based on the stored data. This makes Zabbix ideal for capacity planning.</p>
-<p>For more information and related downloads for Zabbix components, please visit <a href="https://hub.docker.com/u/zabbix/">Docker Hub</a> and <a href="https://zabbix.com">zabbix.com</a></p>
+<p>For more information and related downloads for Zabbix components, please visit <a href="https://zabbix.com">zabbix.com</a></p>
 <h2>What is Zabbix web service?</h2>
 <p>Zabbix web service for performing various tasks using headless web browser (for example, reporting).</p>
 <h2>Zabbix web service images</h2>
@@ -66,16 +66,3 @@ ZBX_IGNOREURLCERTERRORS=0
 <h3>Allowed volumes for the Zabbix web service container</h3>
 <h4><code>/var/lib/zabbix/enc</code></h4>
 <p>The volume is used to store TLS related files. These file names are specified using <code>ZBX_TLSCAFILE</code>, <code>ZBX_TLSCERTFILE</code> and <code>ZBX_TLSKEYFILE</code> variables. Additionally it is possible to use environment variables <code>ZBX_TLSCA</code>, <code>ZBX_TLSCERT</code> and <code>ZBX_TLSKEY</code> with plaintext values.</p>
-<h2>User Feedback</h2>
-<h3>Documentation</h3>
-<p>Documentation for this image is stored in the <a href="https://github.com/zabbix/zabbix-docker/tree/7.4/Dockerfiles/web-service"><code>web-service/</code> directory</a> of the <a href="https://github.com/zabbix/zabbix-docker/"><code>zabbix/zabbix-docker</code> GitHub repo</a>. Be sure to familiarize yourself with the <a href="https://github.com/zabbix/zabbix-docker/blob/7.4/README.md">repository's <code>README.md</code> file</a> before attempting a pull request.</p>
-<h3>Issues</h3>
-<p>If you have any problems with or questions about this image, please contact us through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>.</p>
-<h4>Known issues</h4>
-<p>Zabbix web services uses Google Chromium with headless mode. Because of restrictions you may see the following error during report generation:</p>
-<pre><code>Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
-</code></pre>
-<p>To avoid the issue it is required to add <code>SYS_ADMIN</code> capability for Zabbix web service. The capability is redundant and allow too much.</p>
-<h3>Contributing</h3>
-<p>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.</p>
-<p>Before you start to code, we recommend discussing your plans through a <a href="https://github.com/zabbix/zabbix-docker/issues">GitHub issue</a>, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.</p>