From c34236200292b90dad530deaaddd0a1c6b894ed4 Mon Sep 17 00:00:00 2001 From: Alexey Pustovalov Date: Sat, 11 Jul 2026 21:25:41 +0900 Subject: [PATCH] Fixed variable descriptions --- Dockerfiles/agent/rhel/README.html | 198 ++++++----- Dockerfiles/agent2/rhel/README.html | 200 ++++++----- Dockerfiles/java-gateway/rhel/README.html | 70 ++-- Dockerfiles/proxy-mysql/rhel/README.html | 322 ++++++++++-------- Dockerfiles/proxy-sqlite3/rhel/README.html | 252 +++++++------- Dockerfiles/server-mysql/rhel/README.html | 328 +++++++++--------- Dockerfiles/server-pgsql/rhel/README.html | 337 ++++++++++--------- Dockerfiles/snmptraps/rhel/README.html | 75 +++-- Dockerfiles/web-nginx-mysql/rhel/README.html | 259 ++++++++------ Dockerfiles/web-nginx-pgsql/rhel/README.html | 260 ++++++++------ Dockerfiles/web-service/rhel/README.html | 93 ++--- 11 files changed, 1324 insertions(+), 1070 deletions(-) diff --git a/Dockerfiles/agent/rhel/README.html b/Dockerfiles/agent/rhel/README.html index 9d998f4a..e78de339 100644 --- a/Dockerfiles/agent/rhel/README.html +++ b/Dockerfiles/agent/rhel/README.html @@ -1,126 +1,150 @@ -

logo

-

What is Zabbix?

+

What is Zabbix?

Zabbix is an enterprise-class open source distributed monitoring solution.

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.

-

For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-

What is Zabbix agent?

+

For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+

What is Zabbix agent?

Zabbix agent is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc).

-

Zabbix agent images

-

These are the only official Zabbix agent Docker images.

-

How to use this image

-

Start zabbix-agent

+

Zabbix agent images

+

Images are updated when new releases are published.

+

How to use this image

+

Start zabbix-agent

Start a Zabbix agent container as follows:

-
podman run --name some-zabbix-agent -e ZBX_HOSTNAME="some-hostname" -e ZBX_SERVER_HOST="some-zabbix-server" --init -d zabbix/zabbix-agent:tag
-

Where some-zabbix-agent is the name you want to assign to your container, some-hostname is the hostname, it is Hostname parameter in Zabbix agent configuration file, some-zabbix-server is IP or DNS name of Zabbix server or proxy and tag is the tag specifying the version you want.

-

Connects from Zabbix server or Zabbix proxy in other containers (Passive checks)

+
podman run \
+    --name some-zabbix-agent \
+    -e ZBX_HOSTNAME="some-hostname" \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-agent-74:tag
+
+

Where some-zabbix-agent is the name you want to assign to your container, some-hostname is the hostname, it is Hostname parameter in Zabbix agent configuration file, some-zabbix-server is IP or DNS name of Zabbix server or proxy and tag is the tag specifying the version you want.

+

Connects from Zabbix server or Zabbix proxy in other containers (Passive checks)

This image exposes the standard Zabbix agent port (10050) to perform passive checks, so container linking makes Zabbix agent instance available to Zabbix server and Zabbix proxy containers. Start your application container like this in order to link it to the Zabbix agent container:

-
$ podman run --name some-zabbix-server --link some-zabbix-agent:zabbix-agent --init -d zabbix/zabbix-server:latest
+
$ podman run \
+    --name some-zabbix-server \
+    --link some-zabbix-agent:zabbix-agent \
+    --init \
+    -d zabbix/zabbix-server:latest
 

-
Connect to Zabbix server or Zabbix proxy containers (Active checks)

-
This image supports perform active checks, so container linking makes Zabbix server and Zabbix proxy containers available to Zabbix agent instance. Start your application container like this in order to link Zabbix agent to Zabbix server or Zabbix proxy containterns:

-
$ podman run --name some-zabbix-agent --link some-zabbix-server:zabbix-server --init -d zabbix/zabbix-agent:latest
+
Connect to Zabbix server or Zabbix proxy containers (Active checks)

+
This image supports perform active checks, so container linking makes Zabbix server and Zabbix proxy containers available to Zabbix agent instance. Start your application container like this in order to link Zabbix agent to Zabbix server or Zabbix proxy containers:

+
$ podman run \
+    --name some-zabbix-agent \
+    --link some-zabbix-server:zabbix-server \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-agent-74:latest
 

-
Container shell access and viewing Zabbix agent logs

+
Container shell access and viewing Zabbix agent logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-agent container:

-
$ podman exec -ti some-zabbix-agent /bin/bash
+
$ podman exec -ti some-zabbix-agent /bin/bash
 

-
The Zabbix agent log is available through Podman's container log:

-
$ podman logs some-zabbix-agent
+
The Zabbix agent log is available through Podman's container log:

+
$ podman logs some-zabbix-agent
 

-
Privileged mode

-
By default, Podman containers are "unprivileged" and do not have access to the most of host resources. Zabbix agent is designed to monitor system resources, to do that Zabbix agent container must be privileged or you may mount some system-wide volumes. For example:

-
$ podman run --name some-zabbix-agent --link some-zabbix-server:zabbix-server --privileged --init -d zabbix/zabbix-agent:latest
+
Privileged mode

+
By default, Podman containers are "unprivileged" and do not have access to the most of host resources. Zabbix agent is designed to monitor system resources, to do that Zabbix agent container must be privileged or you may mount some system-wide volumes. For example:

+
$ podman run \
+    --name some-zabbix-agent \
+    --link some-zabbix-server:zabbix-server \
+    --privileged \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-agent-74:latest
 

-
$ podman run --name some-zabbix-agent --link some-zabbix-server:zabbix-server -v /dev/sdc:/dev/sdc --init -d zabbix/zabbix-agent:latest
+
$ podman run \
+    --name some-zabbix-agent \
+    --link some-zabbix-server:zabbix-server \
+    -v /dev/sdc:/dev/sdc \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-agent-74:latest
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-agent image, you can adjust the configuration of the Zabbix agent by passing one or more environment variables on the podman run command line.

-
ZBX_HOSTNAME

+
ZBX_HOSTNAME

 
This variable is unique, case sensitive hostname. By default, value is hostname of the container. It is Hostname parameter in zabbix_agentd.conf.

-
ZBX_SERVER_HOST

+
ZBX_SERVER_HOST

 
This variable is IP or DNS name of Zabbix server or Zabbix proxy. By default, value is zabbix-server. It is Server parameter in zabbix_agentd.conf. It is allowed to specify Zabbix server or Zabbix proxy port number using ZBX_SERVER_PORT variable. It make sense in case of non-default port for active checks.

-
ZBX_PASSIVE_ALLOW

+
ZBX_PASSIVE_ALLOW

 
This variable is boolean (true or false) and enables or disables feature of passive checks. By default, value is true.

-
ZBX_PASSIVESERVERS

+
ZBX_PASSIVESERVERS

 
The variable is comma separated list of allowed Zabbix server or proxy hosts for connections to Zabbix agent container.

-
ZBX_ACTIVE_ALLOW

+
ZBX_ACTIVE_ALLOW

 
This variable is boolean (true or false) and enables or disables feature of active checks. By default, value is true.

-
ZBX_ACTIVESERVERS

+
ZBX_ACTIVESERVERS

 
The variable is comma separated list of allowed Zabbix server or proxy hosts for connections to Zabbix agent container. You may specify port of Zabbix server or Zabbix proxy in such syntax: zabbix-server:10061,zabbix-proxy:10072.

-
ZBX_LOADMODULE

+
ZBX_LOADMODULE

 
The variable is list of comma separated loadable Zabbix modules. It works with  volume /var/lib/zabbix/modules. The syntax of the variable is dummy1.so,dummy2.so.

-
ZBX_DEBUGLEVEL

+
ZBX_DEBUGLEVEL

 
The variable is used to specify debug level. By default, value is 3. It is DebugLevel parameter in zabbix_agentd.conf. Allowed values are listed below:

 
    
 
  • 0 - basic information about starting and stopping of Zabbix processes;
    • 
 
  • 1 - critical information
    • 
 
  • 2 - error information
    • 
 
  • 3 - warnings
    • 
-
  • 4 - for debugging (produces lots of information)
    • 
+
  • 4 -  for debugging (produces lots of information)
    • 
 
  • 5 - extended debugging (produces even more information)
    • 
 

-
ZBX_TIMEOUT

+
ZBX_TIMEOUT

 
The variable is used to specify timeout for processing checks. By default, value is 3.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_SOURCEIP=
-ZBX_ENABLEREMOTECOMMANDS=0 # Deprecated since 5.0.0
-ZBX_LOGREMOTECOMMANDS=0
-ZBX_HEARTBEAT_FREQUENCY=60 # Available since 6.2.0
-ZBX_HOSTINTERFACE= # Available since 4.4.0
-ZBX_HOSTINTERFACEITEM= # Available since 4.4.0
-ZBX_STARTAGENTS=10
-ZBX_HOSTNAMEITEM=system.hostname
-ZBX_METADATA=
-ZBX_METADATAITEM=
-ZBX_REFRESHACTIVECHECKS=5
-ZBX_BUFFERSEND=5
-ZBX_BUFFERSIZE=100
-ZBX_MAXLINESPERSECOND=20
-ZBX_LISTENIP=
-ZBX_LISTENPORT=10050
-ZBX_LISTENBACKLOG=
-ZBX_UNSAFEUSERPARAMETERS=0
-ZBX_TLSCONNECT=unencrypted
-ZBX_TLSACCEPT=unencrypted
-ZBX_TLSCAFILE=
-ZBX_TLSCA=
-ZBX_TLSCRLFILE=
-ZBX_TLSCRL=
-ZBX_TLSSERVERCERTISSUER=
-ZBX_TLSSERVERCERTSUBJECT=
-ZBX_TLSCERTFILE=
-ZBX_TLSCERT=
-ZBX_TLSKEYFILE=
-ZBX_TLSKEY=
-ZBX_TLSPSKIDENTITY=
-ZBX_TLSPSKFILE=
-ZBX_TLSPSK=
-ZBX_TLSCIPHERALL= # Available since 4.4.7
-ZBX_TLSCIPHERALL13= # Available since 4.4.7
-ZBX_TLSCIPHERCERT= # Available since 4.4.7
-ZBX_TLSCIPHERCERT13= # Available since 4.4.7
-ZBX_TLSCIPHERPSK= # Available since 4.4.7
-ZBX_TLSCIPHERPSK13= # Available since 4.4.7
-ZBX_DENYKEY=system.run[*] # Available since 5.0.0
-ZBX_ALLOWKEY= # Available since 5.0.0
-
Default values of these variables are specified after equal sign.

+
ZBX_SOURCEIP=
+ZBX_ENABLEREMOTECOMMANDS=0 # Deprecated since 5.0.0
+ZBX_LOGREMOTECOMMANDS=0
+ZBX_HEARTBEAT_FREQUENCY=60 # Available since 6.2.0
+ZBX_HOSTINTERFACE= # Available since 4.4.0
+ZBX_HOSTINTERFACEITEM= # Available since 4.4.0
+ZBX_STARTAGENTS=10
+ZBX_HOSTNAMEITEM=system.hostname
+ZBX_METADATA=
+ZBX_METADATAITEM=
+ZBX_REFRESHACTIVECHECKS=5
+ZBX_BUFFERSEND=5
+ZBX_BUFFERSIZE=100
+ZBX_MAXLINESPERSECOND=20
+ZBX_LISTENIP=
+ZBX_LISTENPORT=10050
+ZBX_LISTENBACKLOG=
+ZBX_UNSAFEUSERPARAMETERS=0
+ZBX_TLSCONNECT=unencrypted
+ZBX_TLSACCEPT=unencrypted
+ZBX_TLSCAFILE=
+ZBX_TLSCA=
+ZBX_TLSCRLFILE=
+ZBX_TLSCRL=
+ZBX_TLSSERVERCERTISSUER=
+ZBX_TLSSERVERCERTSUBJECT=
+ZBX_TLSCERTFILE=
+ZBX_TLSCERT=
+ZBX_TLSKEYFILE=
+ZBX_TLSKEY=
+ZBX_TLSPSKIDENTITY=
+ZBX_TLSPSKFILE=
+ZBX_TLSPSK=
+ZBX_TLSCIPHERALL= # Available since 4.4.7
+ZBX_TLSCIPHERALL13= # Available since 4.4.7
+ZBX_TLSCIPHERCERT= # Available since 4.4.7
+ZBX_TLSCIPHERCERT13= # Available since 4.4.7
+ZBX_TLSCIPHERPSK= # Available since 4.4.7
+ZBX_TLSCIPHERPSK13= # Available since 4.4.7
+ZBX_DENYKEY=system.run[*] # Available since 5.0.0
+ZBX_ALLOWKEY= # Available since 5.0.0
+

+
Default values of these variables are specified after equal sign.

 
The allowed variables are identical of parameters in official zabbix_agentd.conf configuration file. For example, ZBX_REFRESHACTIVECHECKS = RefreshActiveChecks.

 
Please use official documentation for zabbix_agentd.conf to get more information about the variables.

-
Allowed volumes for the Zabbix agent container

-
/etc/zabbix/zabbix_agentd.d

+
Allowed volumes for the Zabbix agent container

+
/etc/zabbix/zabbix_agentd.d

 
The volume allows include *.conf files and extend Zabbix agent using UserParameter feature.

-
/var/lib/zabbix/modules

+
/var/lib/zabbix/modules

 
The volume allows load additional modules and extend Zabbix agent using LoadModule feature.

-
/var/lib/zabbix/enc

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_TLSCAFILE, ZBX_TLSCRLFILE, ZBX_TLSCERTFILE, ZBX_TLSKEYFILE and ZBX_TLSPSKFILE variables. Additionally it is possible to use environment variables ZBX_TLSCA, ZBX_TLSCRL, ZBX_TLSCERT, ZBX_TLSKEY and ZBX_TLSPSK with plaintext values.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the agent/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the agent/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

+
Known issues

 
Currently it is not allowed to specify ZBX_ALIAS environment variable. Please use /etc/zabbix/zabbix_agentd.d volume with additional configuration files with Alias options.

-
Contributing

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/agent2/rhel/README.html b/Dockerfiles/agent2/rhel/README.html
index 38fafac6..6dc178b0 100644
--- a/Dockerfiles/agent2/rhel/README.html
+++ b/Dockerfiles/agent2/rhel/README.html
@@ -1,53 +1,76 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix agent 2?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix agent 2?

 
Zabbix agent 2 is deployed on a monitoring target to actively monitor local resources and applications (hard drives, memory, processor statistics etc).

-
Zabbix agent 2 images

+
Zabbix agent 2 images

 
Images are updated when new releases are published.

-
How to use this image

-
Start zabbix-agent2

+
How to use this image

+
Start zabbix-agent2

 
Start a Zabbix agent 2 container as follows:

-
podman run --name some-zabbix-agent -e ZBX_HOSTNAME="some-hostname" -e ZBX_SERVER_HOST="some-zabbix-server" --init -d zabbix/zabbix-agent2:tag
-
Where some-zabbix-agent2 is the name you want to assign to your container, some-hostname is the hostname, it is Hostname parameter in Zabbix agent 2 configuration file, some-zabbix-server is IP or DNS name of Zabbix server or proxy and tag is the tag specifying the version you want.

-
Connects from Zabbix server or Zabbix proxy in other containers (Passive checks)

+
podman run \
+    --name some-zabbix-agent \
+    -e ZBX_HOSTNAME="some-hostname" \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-agent2-74:tag
+

+
Where some-zabbix-agent2 is the name you want to assign to your container, some-hostname is the hostname, it is Hostname parameter in Zabbix agent 2 configuration file, some-zabbix-server is IP or DNS name of Zabbix server or proxy and tag is the tag specifying the version you want.

+
Connects from Zabbix server or Zabbix proxy in other containers (Passive checks)

 
This image exposes the standard Zabbix agent 2 port (10050) to perform passive checks, so container linking makes Zabbix agent 2 instance available to Zabbix server and Zabbix proxy containers. Start your application container like this in order to link it to the Zabbix agent 2 container:

-
$ podman run --name some-zabbix-server --link some-zabbix-agent:zabbix-agent2 --init -d zabbix/zabbix-server:latest
+
$ podman run \
+    --name some-zabbix-server \
+    --link some-zabbix-agent:zabbix-agent2 \
+    --init \
+    -d zabbix/zabbix-server:latest
 

-
Connect to Zabbix server or Zabbix proxy containers (Active checks)

-
This image supports perform active checks, so container linking makes Zabbix server and Zabbix proxy containers available to Zabbix agent 2 instance. Start your application container like this in order to link Zabbix agent 2 to Zabbix server or Zabbix proxy containterns:

-
$ podman run --name some-zabbix-agent --link some-zabbix-server:zabbix-server --init -d zabbix/zabbix-agent2:latest
+
Connect to Zabbix server or Zabbix proxy containers (Active checks)

+
This image supports perform active checks, so container linking makes Zabbix server and Zabbix proxy containers available to Zabbix agent 2 instance. Start your application container like this in order to link Zabbix agent 2 to Zabbix server or Zabbix proxy containers:

+
$ podman run \
+    --name some-zabbix-agent \
+    --link some-zabbix-server:zabbix-server \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-agent2-74:latest
 

-
Container shell access and viewing Zabbix agent 2 logs

+
Container shell access and viewing Zabbix agent 2 logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-agent2 container:

-
$ podman exec -ti some-zabbix-agent /bin/bash
+
$ podman exec -ti some-zabbix-agent /bin/bash
 

-
The Zabbix agent 2 log is available through Podman's container log:

-
$ podman logs some-zabbix-agent
+
The Zabbix agent 2 log is available through Podman's container log:

+
$ podman logs some-zabbix-agent
 

-
Privileged mode

-
By default, Podman containers are "unprivileged" and do not have access to the most of host resources. Zabbix agent 2 is designed to monitor system resources, to do that Zabbix agent 2 container must be privileged or you may mount some system-wide volumes. For example:

-
$ podman run --name some-zabbix-agent --link some-zabbix-server:zabbix-server --privileged --init -d zabbix/zabbix-agent2:latest
+
Privileged mode

+
By default, Podman containers are "unprivileged" and do not have access to the most of host resources. Zabbix agent 2 is designed to monitor system resources, to do that Zabbix agent 2 container must be privileged or you may mount some system-wide volumes. For example:

+
$ podman run \
+    --name some-zabbix-agent \
+    --link some-zabbix-server:zabbix-server \
+    --privileged \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-agent2-74:latest
 

-
$ podman run --name some-zabbix-agent --link some-zabbix-server:zabbix-server -v /dev/sdc:/dev/sdc --init -d zabbix/zabbix-agent2:latest
+
$ podman run \
+    --name some-zabbix-agent \
+    --link some-zabbix-server:zabbix-server \
+    -v /dev/sdc:/dev/sdc \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-agent2-74:latest
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-agent2 image, you can adjust the configuration of the Zabbix agent 2 by passing one or more environment variables on the podman run command line.

-
ZBX_HOSTNAME

+
ZBX_HOSTNAME

 
This variable is unique, case sensitive hostname. By default, value is hostname of the container. It is Hostname parameter in zabbix_agent2.conf.

-
ZBX_SERVER_HOST

+
ZBX_SERVER_HOST

 
This variable is IP or DNS name of Zabbix server or Zabbix proxy. By default, value is zabbix-server. It is Server parameter in zabbix_agent2.conf. It is allowed to specify Zabbix server or Zabbix proxy port number using ZBX_SERVER_PORT variable. It make sense in case of non-default port for active checks.

-
ZBX_PASSIVE_ALLOW

+
ZBX_PASSIVE_ALLOW

 
This variable is boolean (true or false) and enables or disables feature of passive checks. By default, value is true.

-
ZBX_PASSIVESERVERS

+
ZBX_PASSIVESERVERS

 
The variable is comma separated list of allowed Zabbix server or proxy hosts for connections to Zabbix agent 2 container.

-
ZBX_ACTIVE_ALLOW

+
ZBX_ACTIVE_ALLOW

 
This variable is boolean (true or false) and enables or disables feature of active checks. By default, value is true.

-
ZBX_ACTIVESERVERS

+
ZBX_ACTIVESERVERS

 
The variable is comma separated list of allowed Zabbix server or proxy hosts for connections to Zabbix agent 2 container. You may specify port of Zabbix server or Zabbix proxy in such syntax: zabbix-server:10061,zabbix-proxy:10072.

-
ZBX_DEBUGLEVEL

+
ZBX_DEBUGLEVEL

 
The variable is used to specify debug level. By default, value is 3. It is DebugLevel parameter in zabbix_agent2.conf. Allowed values are listed below:

 
    
 
  • 0 - basic information about starting and stopping of Zabbix processes;
    • 
@@ -57,72 +80,73 @@
 
  • 4 -  for debugging (produces lots of information)
    • 
 
  • 5 - extended debugging (produces even more information)
    • 
 

-
ZBX_TIMEOUT

+
ZBX_TIMEOUT

 
The variable is used to specify timeout for processing checks. By default, value is 3.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_ENABLEPERSISTENTBUFFER=false # Available since 5.0.0
-ZBX_PERSISTENTBUFFERPERIOD=1h # Available since 5.0.0
-ZBX_ENABLESTATUSPORT=
-ZBX_SOURCEIP=
-ZBX_HEARTBEAT_FREQUENCY=60 # Available since 6.2.0
-ZBX_ENABLEREMOTECOMMANDS=0 # Deprecated since 5.0.0
-ZBX_LOGREMOTECOMMANDS=0
-ZBX_FORCEACTIVECHECKSONSTART=0 # Available since 6.0.2
-ZBX_HOSTINTERFACE= # Available since 4.4.0
-ZBX_HOSTINTERFACEITEM= # Available since 4.4.0
-ZBX_HOSTNAMEITEM=system.hostname
-ZBX_METADATA=
-ZBX_METADATAITEM=
-ZBX_REFRESHACTIVECHECKS=5
-ZBX_BUFFERSEND=5
-ZBX_BUFFERSIZE=1000
-ZBX_MAXLINESPERSECOND=20
-ZBX_EVENTLOGMAXLINESPERSECOND=20 # Windows only
-ZBX_LISTENIP=
-ZBX_LISTENPORT=10050
-ZBX_PLUGINTIMEOUT=
-ZBX_UNSAFEUSERPARAMETERS=0
-ZBX_TLSCONNECT=unencrypted
-ZBX_TLSACCEPT=unencrypted
-ZBX_TLSCAFILE=
-ZBX_TLSCA=
-ZBX_TLSCRLFILE=
-ZBX_TLSCRL=
-ZBX_TLSSERVERCERTISSUER=
-ZBX_TLSSERVERCERTSUBJECT=
-ZBX_TLSCERTFILE=
-ZBX_TLSCERT=
-ZBX_TLSKEYFILE=
-ZBX_TLSKEY=
-ZBX_TLSPSKIDENTITY=
-ZBX_TLSPSKFILE=
-ZBX_TLSPSK=
-ZBX_TLSCIPHERALL=
-ZBX_TLSCIPHERALL13=
-ZBX_TLSCIPHERCERT=
-ZBX_TLSCIPHERCERT13=
-ZBX_TLSCIPHERPSK=
-ZBX_TLSCIPHERPSK13=
-ZBX_DENYKEY=system.run[*] # Available since 5.0.0
-ZBX_ALLOWKEY= # Available since 5.0.0
-
Default values of these variables are specified after equal sign.

+
ZBX_ENABLEPERSISTENTBUFFER=false # Available since 5.0.0
+ZBX_PERSISTENTBUFFERPERIOD=1h # Available since 5.0.0
+ZBX_ENABLESTATUSPORT=
+ZBX_SOURCEIP=
+ZBX_HEARTBEAT_FREQUENCY=60 # Available since 6.2.0
+ZBX_ENABLEREMOTECOMMANDS=0 # Deprecated since 5.0.0
+ZBX_LOGREMOTECOMMANDS=0
+ZBX_FORCEACTIVECHECKSONSTART=0 # Available since 6.0.2
+ZBX_HOSTINTERFACE= # Available since 4.4.0
+ZBX_HOSTINTERFACEITEM= # Available since 4.4.0
+ZBX_HOSTNAMEITEM=system.hostname
+ZBX_METADATA=
+ZBX_METADATAITEM=
+ZBX_REFRESHACTIVECHECKS=5
+ZBX_BUFFERSEND=5
+ZBX_BUFFERSIZE=1000
+ZBX_MAXLINESPERSECOND=20
+ZBX_EVENTLOGMAXLINESPERSECOND=20 # Windows only
+ZBX_LISTENIP=
+ZBX_LISTENPORT=10050
+ZBX_PLUGINTIMEOUT=
+ZBX_UNSAFEUSERPARAMETERS=0
+ZBX_TLSCONNECT=unencrypted
+ZBX_TLSACCEPT=unencrypted
+ZBX_TLSCAFILE=
+ZBX_TLSCA=
+ZBX_TLSCRLFILE=
+ZBX_TLSCRL=
+ZBX_TLSSERVERCERTISSUER=
+ZBX_TLSSERVERCERTSUBJECT=
+ZBX_TLSCERTFILE=
+ZBX_TLSCERT=
+ZBX_TLSKEYFILE=
+ZBX_TLSKEY=
+ZBX_TLSPSKIDENTITY=
+ZBX_TLSPSKFILE=
+ZBX_TLSPSK=
+ZBX_TLSCIPHERALL=
+ZBX_TLSCIPHERALL13=
+ZBX_TLSCIPHERCERT=
+ZBX_TLSCIPHERCERT13=
+ZBX_TLSCIPHERPSK=
+ZBX_TLSCIPHERPSK13=
+ZBX_DENYKEY=system.run[*] # Available since 5.0.0
+ZBX_ALLOWKEY= # Available since 5.0.0
+

+
Default values of these variables are specified after equal sign.

 
The allowed variables are identical of parameters in official zabbix_agent2.conf configuration file. For example, ZBX_REFRESHACTIVECHECKS = RefreshActiveChecks.

 
Please use official documentation for zabbix_agent2.conf to get more information about the variables.

-
Allowed volumes for the Zabbix agent 2 container

-
/etc/zabbix/zabbix_agentd.d

+
Allowed volumes for the Zabbix agent 2 container

+
/etc/zabbix/zabbix_agentd.d

 
The volume allows include *.conf files and extend Zabbix agent 2 using UserParameter feature.

-
/var/lib/zabbix/enc

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_TLSCAFILE, ZBX_TLSCRLFILE, ZBX_TLSCERTFILE, ZBX_TLSKEYFILE and ZBX_TLSPSKFILE variables. Additionally it is possible to use environment variables ZBX_TLSCA, ZBX_TLSCRL, ZBX_TLSCERT, ZBX_TLSKEY and ZBX_TLSPSK with plaintext values.

-
/var/lib/zabbix/buffer

+
/var/lib/zabbix/buffer

 
The volume is used to store the file, where Zabbix Agent2 should keep SQLite database. To enable the feature specify ZBX_ENABLEPERSISTENTBUFFER=true. Available since 5.0.0.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the agent2/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the agent2/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

+
Known issues

 
Currently it is not allowed to specify ZBX_ALIAS environment variable. Please use /etc/zabbix/zabbix_agentd.d volume with additional configuration files with Alias options.

-
Contributing

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/java-gateway/rhel/README.html b/Dockerfiles/java-gateway/rhel/README.html
index df0b5c60..91fb1814 100644
--- a/Dockerfiles/java-gateway/rhel/README.html
+++ b/Dockerfiles/java-gateway/rhel/README.html
@@ -1,47 +1,53 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix Java Gateway?

-
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".

-
Zabbix Java Gateway images

-
These are the only official Zabbix Java Gateway Podman images. Images are updated when new releases are published.

-
How to use this image

-
Start zabbix-java-gateway

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix Java Gateway?

+
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".

+
Zabbix Java Gateway images

+
Images are updated when new releases are published.

+
How to use this image

+
Start zabbix-java-gateway

 
Start a Zabbix Java Gateway container as follows:

-
podman run --name some-zabbix-java-gateway -d zabbix/zabbix-java-gateway:tag
-
Where some-zabbix-java-gateway is the name you want to assign to your container and tag is the tag specifying the version you want.

-
Linking the container to Zabbix server or Zabbix proxy

-
podman run --name some-zabbix-java-gateway --link some-zabbix-server:zabbix-server -d zabbix/zabbix-java-gateway:tag
-
Container shell access and viewing Zabbix Java Gateway logs

+
podman run \
+    --name some-zabbix-java-gateway \
+    -d registry.connect.redhat.com/zabbix/zabbix-java-gateway-74:tag
+

+
Where some-zabbix-java-gateway is the name you want to assign to your container and tag is the tag specifying the version you want.

+
Linking the container to Zabbix server or Zabbix proxy

+
podman run \
+    --name some-zabbix-java-gateway \
+    --link some-zabbix-server:zabbix-server \
+    -d registry.connect.redhat.com/zabbix/zabbix-java-gateway-74:tag
+

+
Container shell access and viewing Zabbix Java Gateway logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-java-gateway container:

-
$ podman exec -ti some-zabbix-java-gateway /bin/bash
+
$ podman exec -ti some-zabbix-java-gateway /bin/bash
 

-
The Zabbix Java Gateway log is available through Podman's container log:

-
$ podman logs  some-zabbix-java-gateway
+
The Zabbix Java Gateway log is available through Podman's container log:

+
$ podman logs  some-zabbix-java-gateway
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-java-gateway image, you can adjust the configuration of the Zabbix Java Gateway by passing one or more environment variables on the podman run command line.

-
ZBX_START_POLLERS

+
ZBX_START_POLLERS

 
This variable is specified amount of pollers. By default, value is 5.

-
ZBX_TIMEOUT

+
ZBX_TIMEOUT

 
This variable is used to specify timeout for outgoing connections. By default, value is 3.

-
ZBX_DEBUGLEVEL

-
This variable is used to specify log level. By default, value is info. The variable allows next values: trace, debug, info, want, error, all, off

-
ZBX_PROPERTIES_FILE

+
ZBX_DEBUGLEVEL

+
This variable is used to specify log level. By default, value is info. The variable allows next values: trace, debug, info, warn, error, all, off

+
ZBX_PROPERTIES_FILE

 
Name of properties file. Can be used to set additional properties using a key-value format in such a way that they are not visible on a command line or to overwrite existing ones.

-
ZABBIX_OPTIONS

+
ZABBIX_OPTIONS

 
Additional arguments for Zabbix Java Gateway. Useful to enable additional libraries and features.

-
Allowed volumes for the Zabbix Java Gateway container

-
/usr/sbin/zabbix_java/ext_lib

+
Allowed volumes for the Zabbix Java Gateway container

+
/usr/sbin/zabbix_java/ext_lib

 
The volume allows include additional JAR files to extend allowed protocols for Zabbix Java Gateway.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the java-gateway/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the java-gateway/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

-
Contributing

+
Known issues

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/proxy-mysql/rhel/README.html b/Dockerfiles/proxy-mysql/rhel/README.html
index 2efc5f7e..da663c6e 100644
--- a/Dockerfiles/proxy-mysql/rhel/README.html
+++ b/Dockerfiles/proxy-mysql/rhel/README.html
@@ -1,12 +1,11 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix proxy?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix proxy?

 
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.

-
Zabbix proxy images

-
These are the only official Zabbix proxy Podman images. Images are updated when new releases are published. The image with latest tag is based on Alpine Linux.

+
Zabbix proxy images

+
Images are updated when new releases are published.

 
The image uses MySQL database to store collected data before sending it to Zabbix server. It uses the next procedure to start:

 
    
 
  • Checking database availability
    • 
@@ -14,13 +13,22 @@
 
  • Checking of having MYSQL_DATABASE database. Creating MYSQL_DATABASE database name if it does not exist
    • 
 
  • Checking of having dbversion table. Creating Zabbix proxy database schema if no dbversion table
    • 
 

-
How to use this image

-
Start zabbix-proxy-mysql

+
How to use this image

+
Start zabbix-proxy-mysql

 
Start a Zabbix proxy container as follows:

-
podman run --name some-zabbix-proxy-mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER="some-user" -e MYSQL_PASSWORD="some-password" -e ZBX_HOSTNAME=some-hostname -e ZBX_SERVER_HOST=some-zabbix-server --init -d zabbix/zabbix-proxy-mysql:tag
-
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.

+
podman run \
+    --name some-zabbix-proxy-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -e MYSQL_USER="some-user" \
+    -e MYSQL_PASSWORD="some-password" \
+    -e ZBX_HOSTNAME=some-hostname \
+    -e ZBX_SERVER_HOST=some-zabbix-server \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-proxy-mysql-74:tag
+

+
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.

 

-
[!NOTE]
+
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
@@ -30,49 +38,75 @@ Additionally fping executing in non-root environments can require sysctl modific
 net.ipv4.ping_group_range=0 1995
 where 1995 is zabbix GID.

 

-
Connects from Zabbix server (Passive proxy)

+
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:

-
$ podman run --name some-zabbix-server --link some-zabbix-proxy-mysql:zabbix-proxy-mysql --init -d zabbix/zabbix-server:latest
+
$ podman run \
+    --name some-zabbix-server \
+    --link some-zabbix-proxy-mysql:zabbix-proxy-mysql \
+    --init \
+    -d zabbix/zabbix-server:latest
 

-
Connect to Zabbix server (Active proxy)

-
This image can operate as Active proxy (default mode). Start your application container like this in order to link Zabbix proxy to Zabbix server containters:

-
$ podman run --name some-zabbix-proxy-mysql --link some-zabbix-server:zabbix-server --init -d zabbix/zabbix-proxy-mysql:latest
+
Connect to Zabbix server (Active proxy)

+
This image can operate as Active proxy (default mode). Start your application container like this in order to link Zabbix proxy to Zabbix server containers:

+
$ podman run \
+    --name some-zabbix-proxy-mysql \
+    --link some-zabbix-server:zabbix-server \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-proxy-mysql-74:latest
 

-
Container shell access and viewing Zabbix proxy logs

+
Container shell access and viewing Zabbix proxy logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-proxy-mysql container:

-
$ podman exec -ti some-zabbix-proxy-mysql /bin/bash
+
$ podman exec -ti some-zabbix-proxy-mysql /bin/bash
 

-
The Zabbix proxy log is available through Podman's container log:

-
$ podman logs some-zabbix-proxy-mysql
+
The Zabbix proxy log is available through Podman's container log:

+
$ podman logs some-zabbix-proxy-mysql
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-proxy-mysql image, you can adjust the configuration of the Zabbix proxy by passing one or more environment variables on the podman run command line.

-
ZBX_PROXYMODE

-
The variable allows to switch Zabbix proxy mode. Bu default, value is 0 - active proxy. Allowed values are 0 - active proxy and 1 - passive proxy.

-
ZBX_HOSTNAME

+
ZBX_PROXYMODE

+
The variable allows to switch Zabbix proxy mode. By default, value is 0 - active proxy. Allowed values are 0 - active proxy and 1 - passive proxy.

+
ZBX_HOSTNAME

 
This variable is unique, case sensitive hostname. By default, value is zabbix-proxy-mysql of the container. It is Hostname parameter in zabbix_proxy.conf.

-
ZBX_SERVER_HOST

+
ZBX_SERVER_HOST

 
This variable is IP or DNS name of Zabbix server. By default, value is zabbix-server. It is Server parameter in zabbix_proxy.conf. For a non-default port, append it to the host using host:port syntax.

-
DB_SERVER_HOST

-
This variable is IP or DNS name of MySQL server. By default, value is 'mysql-server'

-
DB_SERVER_PORT

-
This variable is port of MySQL server. By default, value is '3306'.

-
MYSQL_USER, MYSQL_PASSWORD, MYSQL_USER_FILE, MYSQL_PASSWORD_FILE

+
DB_SERVER_HOST

+
This variable is IP or DNS name of MySQL server. By default, value is 'mysql-server'

+
DB_SERVER_PORT

+
This variable is port of MySQL server. By default, value is '3306'.

+
MYSQL_USER, MYSQL_PASSWORD, MYSQL_USER_FILE, MYSQL_PASSWORD_FILE

 
These variables are used by Zabbix proxy to connect to Zabbix database. With the _FILE 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 MYSQL_USER or MYSQL_USER_FILE!

-
podman run --name some-zabbix-proxy-mysql -e DB_SERVER_HOST="some-mysql-server" -v ./.MYSQL_USER:/run/secrets/MYSQL_USER -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER -v ./.MYSQL_PASSWORD:/run/secrets/MYSQL_PASSWORD -e MYSQL_PASSWORD_FILE=/var/run/secrets/MYSQL_PASSWORD -e ZBX_HOSTNAME=some-hostname -e ZBX_SERVER_HOST=some-zabbix-server --init -d zabbix/zabbix-proxy-mysql:tag
+
podman run \
+    --name some-zabbix-proxy-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -v ./.MYSQL_USER:/run/secrets/MYSQL_USER \
+    -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER \
+    -v ./.MYSQL_PASSWORD:/run/secrets/MYSQL_PASSWORD \
+    -e MYSQL_PASSWORD_FILE=/var/run/secrets/MYSQL_PASSWORD \
+    -e ZBX_HOSTNAME=some-hostname \
+    -e ZBX_SERVER_HOST=some-zabbix-server \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-proxy-mysql-74:tag
 

 
With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!

-
printf "zabbix" | podman secret create MYSQL_USER -
-printf "zabbix" | podman secret create MYSQL_PASSWORD -
-podman run --name some-zabbix-proxy-mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER -e MYSQL_PASSWORD_FILE=/run/secrets/MYSQL_PASSWORD -e ZBX_SERVER_HOST="some-zabbix-server" -e ZBX_HOSTNAME=some-hostname --init -d zabbix/zabbix-proxy-mysql:tag
+
printf "zabbix" | podman secret create MYSQL_USER -
+printf "zabbix" | podman secret create MYSQL_PASSWORD -
+podman run \
+    --name some-zabbix-proxy-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER \
+    -e MYSQL_PASSWORD_FILE=/run/secrets/MYSQL_PASSWORD \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e ZBX_HOSTNAME=some-hostname \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-proxy-mysql-74:tag
 

 
This method is also applicable for MYSQL_ROOT_PASSWORD with MYSQL_ROOT_PASSWORD_FILE.

 
By default, values for MYSQL_USER and MYSQL_PASSWORD are zabbix, zabbix.

-
MYSQL_DATABASE

+
MYSQL_DATABASE

 
The variable is Zabbix database name. By default, value is zabbix_proxy.

-
ZBX_LOADMODULE

+
ZBX_LOADMODULE

 
The variable is list of comma separated loadable Zabbix modules. It works with  volume /var/lib/zabbix/modules. The syntax of the variable is dummy1.so,dummy2.so.

-
ZBX_DEBUGLEVEL

+
ZBX_DEBUGLEVEL

 
The variable is used to specify debug level. By default, value is 3. It is DebugLevel parameter in zabbix_server.conf. Allowed values are listed below:

 
    
 
  • 0 - basic information about starting and stopping of Zabbix processes;
    • 
@@ -82,124 +116,126 @@ podman run --name some-zabbix-proxy-mysql -e DB_SERV
 
  • 4 - for debugging (produces lots of information)
    • 
 
  • 5 - extended debugging (produces even more information)
    • 
 

-
ZBX_TIMEOUT

+
ZBX_TIMEOUT

 
The variable is used to specify timeout for processing checks. By default, value is 4.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_ALLOWUNSUPPORTEDDBVERSIONS=0 # Available since 6.0.0
-ZBX_DBTLSCONNECT= # Available since 5.0.0
-ZBX_DBTLSCAFILE= # Available since 5.0.0
-ZBX_DBTLSCERTFILE= # Available since 5.0.0
-ZBX_DBTLSKEYFILE= # Available since 5.0.0
-ZBX_DBTLSCIPHER= # Available since 5.0.0
-ZBX_DBTLSCIPHER13= # Available since 5.0.0
-ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
-ZBX_VAULTDBPATH= # Available since 5.2.0
-ZBX_VAULTPREFIX= # Available since 7.0.0
-ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
-VAULT_TOKEN= # Available since 5.2.0
-ZBX_VAULTTLSCERTFILE= # Available since 6.2.0
-ZBX_VAULTTLSKEYFILE= # Available since 6.2.0
-ZBX_ENABLEREMOTECOMMANDS=0 # Available since 3.4.0
-ZBX_LOGREMOTECOMMANDS=0 # Available since 3.4.0
-ZBX_HOSTNAMEITEM=system.hostname
-ZBX_SOURCEIP=
-ZBX_PROXYLOCALBUFFER=0
-ZBX_PROXYOFFLINEBUFFER=1
-ZBX_PROXYBUFFERMODE=disk # Available since 7.0.0
-ZBX_PROXYMEMORYBUFFERAGE=0 # Available since 7.0.0
-ZBX_PROXYMEMORYBUFFERSIZE=0 # Available since 7.0.0
-ZBX_PROXYCONFIGFREQUENCY=10 # Available since 6.4.0
-ZBX_DATASENDERFREQUENCY=1
-ZBX_MAXCONCURRENTCHECKSPERPOLLER=1000 # Available since 7.0.0
-ZBX_STARTAGENTPOLLERS=1 # Available since 7.0.0
-ZBX_STARTHTTPAGENTPOLLERS=1 # Available since 7.0.0
-ZBX_STARTPOLLERS=5
-ZBX_STARTPREPROCESSORS=16 # Available since 4.2.0
-ZBX_STARTIPMIPOLLERS=0
-ZBX_STARTPOLLERSUNREACHABLE=1
-ZBX_STARTTRAPPERS=5
-ZBX_STARTPINGERS=1
-ZBX_STARTDISCOVERERS=5
-ZBX_STARTHTTPPOLLERS=1
-ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
-ZBX_JAVAGATEWAY=zabbix-java-gateway
-ZBX_JAVAGATEWAYPORT=10052
-ZBX_STARTJAVAPOLLERS=0
-ZBX_STATSALLOWEDIP= # Available since 4.0.5
-ZBX_STARTVMWARECOLLECTORS=0
-ZBX_VMWAREFREQUENCY=60
-ZBX_VMWAREPERFFREQUENCY=60
-ZBX_VMWARECACHESIZE=8M
-ZBX_VMWARETIMEOUT=10
-ZBX_ENABLE_SNMP_TRAPS=false
-ZBX_LISTENIP=
-ZBX_LISTENPORT=10051
-ZBX_LISTENBACKLOG=
-ZBX_HOUSEKEEPINGFREQUENCY=1
-ZBX_CACHESIZE=32M
-ZBX_STARTDBSYNCERS=4
-ZBX_HISTORYCACHESIZE=16M
-ZBX_HISTORYINDEXCACHESIZE=4M
-ZBX_TRAPPERTIMEOUT=300
-ZBX_UNREACHABLEPERIOD=45
-ZBX_UNAVAILABLEDELAY=60
-ZBX_UNREACHABLEDELAY=15
-ZBX_LOGSLOWQUERIES=3000
-ZBX_TLSLISTEN= # Available since 7.4.0
-ZBX_TLSCONNECT=unencrypted
-ZBX_TLSACCEPT=unencrypted
-ZBX_TLSCAFILE=
-ZBX_TLSCA=
-ZBX_TLSCRLFILE=
-ZBX_TLSCRL=
-ZBX_TLSSERVERCERTISSUER=
-ZBX_TLSSERVERCERTSUBJECT=
-ZBX_TLSCERTFILE=
-ZBX_TLSCERT=
-ZBX_TLSKEYFILE=
-ZBX_TLSKEY=
-ZBX_TLSPSKIDENTITY=
-ZBX_TLSPSKFILE=
-ZBX_TLSPSK=
-ZBX_TLSCIPHERALL= # Available since 4.4.7
-ZBX_TLSCIPHERALL13= # Available since 4.4.7
-ZBX_TLSCIPHERCERT= # Available since 4.4.7
-ZBX_TLSCIPHERCERT13= # Available since 4.4.7
-ZBX_TLSCIPHERPSK= # Available since 4.4.7
-ZBX_TLSCIPHERPSK13= # Available since 4.4.7
-ZBX_WEBDRIVERURL= # Available since 7.0.0
-ZBX_STARTBROWSERPOLLERS=1 # Available since 7.0.0
-ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
-
Default values of these variables are specified after equal sign.

+
ZBX_ALLOWUNSUPPORTEDDBVERSIONS=0 # Available since 6.0.0
+ZBX_DBTLSCONNECT= # Available since 5.0.0
+ZBX_DBTLSCAFILE= # Available since 5.0.0
+ZBX_DBTLSCERTFILE= # Available since 5.0.0
+ZBX_DBTLSKEYFILE= # Available since 5.0.0
+ZBX_DBTLSCIPHER= # Available since 5.0.0
+ZBX_DBTLSCIPHER13= # Available since 5.0.0
+ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
+ZBX_VAULTDBPATH= # Available since 5.2.0
+ZBX_VAULTPREFIX= # Available since 7.0.0
+ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
+VAULT_TOKEN= # Available since 5.2.0
+ZBX_VAULTTLSCERTFILE= # Available since 6.2.0
+ZBX_VAULTTLSKEYFILE= # Available since 6.2.0
+ZBX_ENABLEREMOTECOMMANDS=0 # Available since 3.4.0
+ZBX_LOGREMOTECOMMANDS=0 # Available since 3.4.0
+ZBX_HOSTNAMEITEM=system.hostname
+ZBX_SOURCEIP=
+ZBX_PROXYLOCALBUFFER=0
+ZBX_PROXYOFFLINEBUFFER=1
+ZBX_PROXYBUFFERMODE=disk # Available since 7.0.0
+ZBX_PROXYMEMORYBUFFERAGE=0 # Available since 7.0.0
+ZBX_PROXYMEMORYBUFFERSIZE=0 # Available since 7.0.0
+ZBX_PROXYCONFIGFREQUENCY=10 # Available since 6.4.0
+ZBX_DATASENDERFREQUENCY=1
+ZBX_MAXCONCURRENTCHECKSPERPOLLER=1000 # Available since 7.0.0
+ZBX_STARTAGENTPOLLERS=1 # Available since 7.0.0
+ZBX_STARTHTTPAGENTPOLLERS=1 # Available since 7.0.0
+ZBX_STARTPOLLERS=5
+ZBX_STARTPREPROCESSORS=16 # Available since 4.2.0
+ZBX_STARTIPMIPOLLERS=0
+ZBX_STARTPOLLERSUNREACHABLE=1
+ZBX_STARTTRAPPERS=5
+ZBX_STARTPINGERS=1
+ZBX_STARTDISCOVERERS=5
+ZBX_STARTHTTPPOLLERS=1
+ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
+ZBX_JAVAGATEWAY=zabbix-java-gateway
+ZBX_JAVAGATEWAYPORT=10052
+ZBX_STARTJAVAPOLLERS=0
+ZBX_STATSALLOWEDIP= # Available since 4.0.5
+ZBX_STARTVMWARECOLLECTORS=0
+ZBX_VMWAREFREQUENCY=60
+ZBX_VMWAREPERFFREQUENCY=60
+ZBX_VMWARECACHESIZE=8M
+ZBX_VMWARETIMEOUT=10
+ZBX_ENABLE_SNMP_TRAPS=false
+ZBX_LISTENIP=
+ZBX_LISTENPORT=10051
+ZBX_LISTENBACKLOG=
+ZBX_HOUSEKEEPINGFREQUENCY=1
+ZBX_CACHESIZE=32M
+ZBX_STARTDBSYNCERS=4
+ZBX_HISTORYCACHESIZE=16M
+ZBX_HISTORYINDEXCACHESIZE=4M
+ZBX_TRAPPERTIMEOUT=300
+ZBX_UNREACHABLEPERIOD=45
+ZBX_UNAVAILABLEDELAY=60
+ZBX_UNREACHABLEDELAY=15
+ZBX_LOGSLOWQUERIES=3000
+ZBX_TLSLISTEN= # Available since 7.4.0
+ZBX_TLSCONNECT=unencrypted
+ZBX_TLSACCEPT=unencrypted
+ZBX_TLSCAFILE=
+ZBX_TLSCA=
+ZBX_TLSCRLFILE=
+ZBX_TLSCRL=
+ZBX_TLSSERVERCERTISSUER=
+ZBX_TLSSERVERCERTSUBJECT=
+ZBX_TLSCERTFILE=
+ZBX_TLSCERT=
+ZBX_TLSKEYFILE=
+ZBX_TLSKEY=
+ZBX_TLSPSKIDENTITY=
+ZBX_TLSPSKFILE=
+ZBX_TLSPSK=
+ZBX_TLSCIPHERALL= # Available since 4.4.7
+ZBX_TLSCIPHERALL13= # Available since 4.4.7
+ZBX_TLSCIPHERCERT= # Available since 4.4.7
+ZBX_TLSCIPHERCERT13= # Available since 4.4.7
+ZBX_TLSCIPHERPSK= # Available since 4.4.7
+ZBX_TLSCIPHERPSK13= # Available since 4.4.7
+ZBX_WEBDRIVERURL= # Available since 7.0.0
+ZBX_STARTBROWSERPOLLERS=1 # Available since 7.0.0
+ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
+
+

+
Default values of these variables are specified after equal sign.

 
The allowed variables are identical of parameters in official zabbix_proxy.conf. For example, ZBX_LOGSLOWQUERIES = LogSlowQueries.

 
Please use official documentation for zabbix_proxy.conf to get more information about the variables.

-
Allowed volumes for the Zabbix proxy container

-
/usr/lib/zabbix/externalscripts

+
Allowed volumes for the Zabbix proxy container

+
/usr/lib/zabbix/externalscripts

 
The volume is used by External checks (type of items). It is ExternalScripts parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/modules

+
/var/lib/zabbix/modules

 
The volume allows load additional modules and extend Zabbix proxy using LoadModule feature.

-
/var/lib/zabbix/enc

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_TLSCAFILE, ZBX_TLSCRLFILE, ZBX_TLSCERTFILE, ZBX_TLSKEYFILE and ZBX_TLSPSKFILE variables. Additionally it is possible to use environment variables ZBX_TLSCA, ZBX_TLSCRL, ZBX_TLSCERT, ZBX_TLSKEY and ZBX_TLSPSK with plaintext values.

-
/var/lib/zabbix/ssh_keys

+
/var/lib/zabbix/ssh_keys

 
The volume is used as location of public and private keys for SSH checks and actions. It is SSHKeyLocation parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/ssl/certs

-
The volume is used as location of of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/ssl/keys

+
/var/lib/zabbix/ssl/certs

+
The volume is used as location of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_proxy.conf.

+
/var/lib/zabbix/ssl/keys

 
The volume is used as location of SSL private key files for client authentication. It is SSLKeyLocation parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/ssl/ssl_ca

+
/var/lib/zabbix/ssl/ssl_ca

 
The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is SSLCALocation parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/snmptraps

+
/var/lib/zabbix/snmptraps

 
The volume is used as location of snmptraps.log file. It could be shared by zabbix-snmptraps container and inherited using volumes_from Podman option while creating new instance of Zabbix proxy.
 SNMP traps processing feature could be enabled using shared volume and switched ZBX_ENABLE_SNMP_TRAPS environment variable to true.

-
/var/lib/zabbix/mibs

-
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed to /var/lib/zabbix/mibs.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the proxy-mysql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
/var/lib/zabbix/mibs

+
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in /var/lib/zabbix/mibs.

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the proxy-mysql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

-
Contributing

+
Known issues

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/proxy-sqlite3/rhel/README.html b/Dockerfiles/proxy-sqlite3/rhel/README.html
index 845e2b6c..3bddd1bd 100644
--- a/Dockerfiles/proxy-sqlite3/rhel/README.html
+++ b/Dockerfiles/proxy-sqlite3/rhel/README.html
@@ -1,20 +1,25 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix proxy?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix proxy?

 
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.

-
Zabbix proxy images

-
These are the only official Zabbix proxy Podman images. Images are updated when new releases are published.

+
Zabbix proxy images

+
Images are updated when new releases are published.

 
The image uses SQLite3 database to store collected data before sending it to Zabbix server.

-
How to use this image

-
Start zabbix-proxy-sqlite3

+
How to use this image

+
Start zabbix-proxy-sqlite3

 
Start a Zabbix proxy container as follows:

-
podman run --name some-zabbix-proxy-sqlite3 -e ZBX_HOSTNAME=some-hostname -e ZBX_SERVER_HOST=some-zabbix-server --init -d zabbix/zabbix-proxy-sqlite3:tag
-
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.

+
podman run \
+    --name some-zabbix-proxy-sqlite3 \
+    -e ZBX_HOSTNAME=some-hostname \
+    -e ZBX_SERVER_HOST=some-zabbix-server \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-proxy-sqlite-74:tag
+

+
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.

 

-
[!NOTE]
+
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
@@ -24,32 +29,40 @@ Additionally fping executing in non-root environments can require sysctl modific
 net.ipv4.ping_group_range=0 1995
 where 1995 is zabbix GID.

 

-
Connects from Zabbix server (Passive proxy)

+
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:

-
$ podman run --name some-zabbix-server --link some-zabbix-proxy-sqlite3:zabbix-proxy-sqlite3 --init -d zabbix/zabbix-server:latest
+
$ podman run \
+    --name some-zabbix-server \
+    --link some-zabbix-proxy-sqlite3:zabbix-proxy-sqlite3 \
+    --init \
+    -d zabbix/zabbix-server:latest
 

-
Connect to Zabbix server (Active proxy)

+
Connect to Zabbix server (Active proxy)

 
This image can operate as Active proxy (default mode). Start your application container like this in order to link Zabbix proxy to Zabbix server containters:

-
$ podman run --name some-zabbix-proxy-sqlite3 --link some-zabbix-server:zabbix-server --init -d zabbix/zabbix-proxy-sqlite3:latest
+
$ podman run \
+    --name some-zabbix-proxy-sqlite3 \
+    --link some-zabbix-server:zabbix-server \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-proxy-sqlite-74:latest
 

-
Container shell access and viewing Zabbix proxy logs

+
Container shell access and viewing Zabbix proxy logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-proxy-sqlite3 container:

-
$ podman exec -ti some-zabbix-proxy-sqlite3 /bin/bash
+
$ podman exec -ti some-zabbix-proxy-sqlite3 /bin/bash
 

-
The Zabbix proxy log is available through Podman's container log:

-
$ podman logs some-zabbix-proxy-sqlite3
+
The Zabbix proxy log is available through Podman's container log:

+
$ podman logs some-zabbix-proxy-sqlite3
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-proxy-sqlite3 image, you can adjust the configuration of the Zabbix proxy by passing one or more environment variables on the podman run command line.

-
ZBX_PROXYMODE

+
ZBX_PROXYMODE

 
The variable allows to switch Zabbix proxy mode. Bu default, value is 0 - active proxy. Allowed values are 0 - active proxy and 1 - passive proxy.

-
ZBX_HOSTNAME

+
ZBX_HOSTNAME

 
This variable is unique, case sensitive hostname. By default, value is zabbix-proxy-sqlite3 of the container. It is Hostname parameter in zabbix_proxy.conf.

-
ZBX_SERVER_HOST

+
ZBX_SERVER_HOST

 
This variable is IP or DNS name of Zabbix server. By default, value is zabbix-server. It is Server parameter in zabbix_proxy.conf. For a non-default port, append it to the host using host:port syntax.

-
ZBX_LOADMODULE

+
ZBX_LOADMODULE

 
The variable is list of comma separated loadable Zabbix modules. It works with  volume /var/lib/zabbix/modules. The syntax of the variable is dummy1.so,dummy2.so.

-
ZBX_DEBUGLEVEL

+
ZBX_DEBUGLEVEL

 
The variable is used to specify debug level. By default, value is 3. It is DebugLevel parameter in zabbix_server.conf. Allowed values are listed below:

 
    
 
  • 0 - basic information about starting and stopping of Zabbix processes;
    • 
@@ -59,113 +72,114 @@ where 1995 is zabbix GID.
    
 
  • 4 - for debugging (produces lots of information)
    • 
 
  • 5 - extended debugging (produces even more information)
    • 
 

-
ZBX_TIMEOUT

+
ZBX_TIMEOUT

 
The variable is used to specify timeout for processing checks. By default, value is 4.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_USE_NODE_NAME_AS_DB_NAME=false
-ZBX_ENABLEREMOTECOMMANDS=0 # Available since 3.4.0
-ZBX_LOGREMOTECOMMANDS=0 # Available since 3.4.0
-ZBX_SOURCEIP=
-ZBX_HOSTNAMEITEM=system.hostname
-ZBX_PROXYLOCALBUFFER=0
-ZBX_PROXYOFFLINEBUFFER=1
-ZBX_PROXYBUFFERMODE=disk # Available since 7.0.0
-ZBX_PROXYMEMORYBUFFERAGE=0 # Available since 7.0.0
-ZBX_PROXYMEMORYBUFFERSIZE=0 # Available since 7.0.0
-ZBX_PROXYCONFIGFREQUENCY=10 # Available since 6.4.0
-ZBX_DATASENDERFREQUENCY=1
-ZBX_MAXCONCURRENTCHECKSPERPOLLER=1000 # Available since 7.0.0
-ZBX_STARTAGENTPOLLERS=1 # Available since 7.0.0
-ZBX_STARTHTTPAGENTPOLLERS=1 # Available since 7.0.0
-ZBX_STARTPOLLERS=5
-ZBX_STARTPREPROCESSORS=16 # Available since 4.2.0
-ZBX_STARTIPMIPOLLERS=0
-ZBX_STARTPOLLERSUNREACHABLE=1
-ZBX_STARTTRAPPERS=5
-ZBX_STARTPINGERS=1
-ZBX_STARTDISCOVERERS=5
-ZBX_STARTHTTPPOLLERS=1
-ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
-ZBX_JAVAGATEWAY=zabbix-java-gateway
-ZBX_JAVAGATEWAYPORT=10052
-ZBX_STARTJAVAPOLLERS=0
-ZBX_STATSALLOWEDIP= # Available since 4.0.5
-ZBX_STARTVMWARECOLLECTORS=0
-ZBX_VMWAREFREQUENCY=60
-ZBX_VMWAREPERFFREQUENCY=60
-ZBX_VMWARECACHESIZE=8M
-ZBX_VMWARETIMEOUT=10
-ZBX_ENABLE_SNMP_TRAPS=false
-ZBX_LISTENIP=
-ZBX_LISTENPORT=10051
-ZBX_LISTENBACKLOG=
-ZBX_HOUSEKEEPINGFREQUENCY=1
-ZBX_CACHESIZE=32M
-ZBX_STARTDBSYNCERS=4
-ZBX_HISTORYCACHESIZE=16M
-ZBX_HISTORYINDEXCACHESIZE=4M
-ZBX_TRAPPERTIMEOUT=300
-ZBX_UNREACHABLEPERIOD=45
-ZBX_UNAVAILABLEDELAY=60
-ZBX_UNREACHABLEDELAY=15
-ZBX_LOGSLOWQUERIES=3000
-ZBX_TLSLISTEN= # Available since 7.4.0
-ZBX_TLSCONNECT=unencrypted
-ZBX_TLSACCEPT=unencrypted
-ZBX_TLSCAFILE=
-ZBX_TLSCA=
-ZBX_TLSCRLFILE=
-ZBX_TLSCRL=
-ZBX_TLSSERVERCERTISSUER=
-ZBX_TLSSERVERCERTSUBJECT=
-ZBX_TLSCERTFILE=
-ZBX_TLSCERT=
-ZBX_TLSKEYFILE=
-ZBX_TLSKEY=
-ZBX_TLSPSKIDENTITY=
-ZBX_TLSPSKFILE=
-ZBX_TLSPSK=
-ZBX_TLSCIPHERALL= # Available since 4.4.7
-ZBX_TLSCIPHERALL13= # Available since 4.4.7
-ZBX_TLSCIPHERCERT= # Available since 4.4.7
-ZBX_TLSCIPHERCERT13= # Available since 4.4.7
-ZBX_TLSCIPHERPSK= # Available since 4.4.7
-ZBX_TLSCIPHERPSK13= # Available since 4.4.7
-ZBX_WEBDRIVERURL= # Available since 7.0.0
-ZBX_STARTBROWSERPOLLERS=1 # Available since 7.0.0
-ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
-
Default values of these variables are specified after equal sign.

+
ZBX_USE_NODE_NAME_AS_DB_NAME=false
+ZBX_ENABLEREMOTECOMMANDS=0 # Available since 3.4.0
+ZBX_LOGREMOTECOMMANDS=0 # Available since 3.4.0
+ZBX_SOURCEIP=
+ZBX_HOSTNAMEITEM=system.hostname
+ZBX_PROXYLOCALBUFFER=0
+ZBX_PROXYOFFLINEBUFFER=1
+ZBX_PROXYBUFFERMODE=disk # Available since 7.0.0
+ZBX_PROXYMEMORYBUFFERAGE=0 # Available since 7.0.0
+ZBX_PROXYMEMORYBUFFERSIZE=0 # Available since 7.0.0
+ZBX_PROXYCONFIGFREQUENCY=10 # Available since 6.4.0
+ZBX_DATASENDERFREQUENCY=1
+ZBX_MAXCONCURRENTCHECKSPERPOLLER=1000 # Available since 7.0.0
+ZBX_STARTAGENTPOLLERS=1 # Available since 7.0.0
+ZBX_STARTHTTPAGENTPOLLERS=1 # Available since 7.0.0
+ZBX_STARTPOLLERS=5
+ZBX_STARTPREPROCESSORS=16 # Available since 4.2.0
+ZBX_STARTIPMIPOLLERS=0
+ZBX_STARTPOLLERSUNREACHABLE=1
+ZBX_STARTTRAPPERS=5
+ZBX_STARTPINGERS=1
+ZBX_STARTDISCOVERERS=5
+ZBX_STARTHTTPPOLLERS=1
+ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
+ZBX_JAVAGATEWAY=zabbix-java-gateway
+ZBX_JAVAGATEWAYPORT=10052
+ZBX_STARTJAVAPOLLERS=0
+ZBX_STATSALLOWEDIP= # Available since 4.0.5
+ZBX_STARTVMWARECOLLECTORS=0
+ZBX_VMWAREFREQUENCY=60
+ZBX_VMWAREPERFFREQUENCY=60
+ZBX_VMWARECACHESIZE=8M
+ZBX_VMWARETIMEOUT=10
+ZBX_ENABLE_SNMP_TRAPS=false
+ZBX_LISTENIP=
+ZBX_LISTENPORT=10051
+ZBX_LISTENBACKLOG=
+ZBX_HOUSEKEEPINGFREQUENCY=1
+ZBX_CACHESIZE=32M
+ZBX_STARTDBSYNCERS=4
+ZBX_HISTORYCACHESIZE=16M
+ZBX_HISTORYINDEXCACHESIZE=4M
+ZBX_TRAPPERTIMEOUT=300
+ZBX_UNREACHABLEPERIOD=45
+ZBX_UNAVAILABLEDELAY=60
+ZBX_UNREACHABLEDELAY=15
+ZBX_LOGSLOWQUERIES=3000
+ZBX_TLSLISTEN= # Available since 7.4.0
+ZBX_TLSCONNECT=unencrypted
+ZBX_TLSACCEPT=unencrypted
+ZBX_TLSCAFILE=
+ZBX_TLSCA=
+ZBX_TLSCRLFILE=
+ZBX_TLSCRL=
+ZBX_TLSSERVERCERTISSUER=
+ZBX_TLSSERVERCERTSUBJECT=
+ZBX_TLSCERTFILE=
+ZBX_TLSCERT=
+ZBX_TLSKEYFILE=
+ZBX_TLSKEY=
+ZBX_TLSPSKIDENTITY=
+ZBX_TLSPSKFILE=
+ZBX_TLSPSK=
+ZBX_TLSCIPHERALL= # Available since 4.4.7
+ZBX_TLSCIPHERALL13= # Available since 4.4.7
+ZBX_TLSCIPHERCERT= # Available since 4.4.7
+ZBX_TLSCIPHERCERT13= # Available since 4.4.7
+ZBX_TLSCIPHERPSK= # Available since 4.4.7
+ZBX_TLSCIPHERPSK13= # Available since 4.4.7
+ZBX_WEBDRIVERURL= # Available since 7.0.0
+ZBX_STARTBROWSERPOLLERS=1 # Available since 7.0.0
+ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
+

+
Default values of these variables are specified after equal sign.

 
The allowed variables are identical of parameters in official zabbix_proxy.conf. For example, ZBX_LOGSLOWQUERIES = LogSlowQueries.

 
Please use official documentation for zabbix_proxy.conf to get more information about the variables.

-
Allowed volumes for the Zabbix proxy container

-
/usr/lib/zabbix/externalscripts

+
Allowed volumes for the Zabbix proxy container

+
/usr/lib/zabbix/externalscripts

 
The volume is used by External checks (type of items). It is ExternalScripts parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/db_data

+
/var/lib/zabbix/db_data

 
The volume stores SQLite3 database file and could be used for external database file storage.

-
/var/lib/zabbix/modules

+
/var/lib/zabbix/modules

 
The volume allows load additional modules and extend Zabbix proxy using LoadModule feature.

-
/var/lib/zabbix/enc

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_TLSCAFILE, ZBX_TLSCRLFILE, ZBX_TLSCERTFILE, ZBX_TLSKEYFILE and ZBX_TLSPSKFILE variables. Additionally it is possible to use environment variables ZBX_TLSCA, ZBX_TLSCRL, ZBX_TLSCERT, ZBX_TLSKEY and ZBX_TLSPSK with plaintext values.

-
/var/lib/zabbix/ssh_keys

+
/var/lib/zabbix/ssh_keys

 
The volume is used as location of public and private keys for SSH checks and actions. It is SSHKeyLocation parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/ssl/certs

-
The volume is used as location of of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/ssl/keys

+
/var/lib/zabbix/ssl/certs

+
The volume is used as location of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_proxy.conf.

+
/var/lib/zabbix/ssl/keys

 
The volume is used as location of SSL private key files for client authentication. It is SSLKeyLocation parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/ssl/ssl_ca

+
/var/lib/zabbix/ssl/ssl_ca

 
The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is SSLCALocation parameter in zabbix_proxy.conf.

-
/var/lib/zabbix/snmptraps

+
/var/lib/zabbix/snmptraps

 
The volume is used as location of snmptraps.log file. It could be shared by zabbix-snmptraps container and inherited using volumes_from Podman option while creating new instance of Zabbix proxy.
 SNMP traps processing feature could be enabled using shared volume and switched ZBX_ENABLE_SNMP_TRAPS environment variable to true.

-
/var/lib/zabbix/mibs

-
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed to /var/lib/zabbix/mibs.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the proxy-sqlite3/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
/var/lib/zabbix/mibs

+
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in /var/lib/zabbix/mibs.

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the proxy-sqlite3/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

-
Contributing

+
Known issues

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/server-mysql/rhel/README.html b/Dockerfiles/server-mysql/rhel/README.html
index c8cc7b3e..7d004c9f 100644
--- a/Dockerfiles/server-mysql/rhel/README.html
+++ b/Dockerfiles/server-mysql/rhel/README.html
@@ -1,12 +1,11 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix server?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix server?

 
Zabbix server is the central process of Zabbix software.

 
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.

-
Zabbix server images

+
Zabbix server images

 
Images are updated when new releases are published.

 
The image uses MySQL database. It uses the next procedure to start:

 
    
@@ -15,13 +14,20 @@
 
  • Checking of having MYSQL_DATABASE database. Creating MYSQL_DATABASE database name if it does not exist
    • 
 
  • Checking of having dbversion table. Creating Zabbix server database schema and upload initial data sample if no dbversion table
    • 
 

-
How to use this image

-
Start zabbix-server-mysql

+
How to use this image

+
Start zabbix-server-mysql

 
Start a Zabbix server container as follows:

-
podman run --name some-zabbix-server-mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER="some-user" -e MYSQL_PASSWORD="some-password" --init -d zabbix/zabbix-server-mysql-74:tag
-
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.

+
podman run \
+    --name some-zabbix-server-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -e MYSQL_USER="some-user" \
+    -e MYSQL_PASSWORD="some-password" \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-server-mysql-74:tag
+

+
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.

 

-
[!NOTE]
+
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
@@ -31,35 +37,49 @@ Additionally fping executing in non-root environments can require sysctl modific
 net.ipv4.ping_group_range=0 1995
 where 1995 is zabbix GID.

 

-
Container shell access and viewing Zabbix server logs

+
Container shell access and viewing Zabbix server logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-server-mysql container:

-
$ podman exec -ti some-zabbix-server-mysql /bin/bash
+
$ podman exec -ti some-zabbix-server-mysql /bin/bash
 

-
The Zabbix server log is available through Podman's container log:

-
$ podman logs some-zabbix-server-mysql
+
The Zabbix server log is available through Podman's container log:

+
$ podman logs some-zabbix-server-mysql
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-server-mysql image, you can adjust the configuration of the Zabbix server by passing one or more environment variables on the podman run command line.

-
DB_SERVER_HOST

-
This variable is IP or DNS name of MySQL server. By default, value is 'mysql-server'

-
DB_SERVER_PORT

-
This variable is port of MySQL server. By default, value is '3306'.

-
MYSQL_USER, MYSQL_PASSWORD, MYSQL_USER_FILE, MYSQL_PASSWORD_FILE

+
DB_SERVER_HOST

+
This variable is IP or DNS name of MySQL server. By default, value is 'mysql-server'

+
DB_SERVER_PORT

+
This variable is port of MySQL server. By default, value is '3306'.

+
MYSQL_USER, MYSQL_PASSWORD, MYSQL_USER_FILE, MYSQL_PASSWORD_FILE

 
These variables are used by Zabbix server to connect to Zabbix database. With the _FILE 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 MYSQL_USER or MYSQL_USER_FILE!

-
podman run --name some-zabbix-server-mysql -e DB_SERVER_HOST="some-mysql-server" -v ./.MYSQL_USER:/run/secrets/MYSQL_USER -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER -v ./.MYSQL_PASSWORD:/run/secrets/MYSQL_PASSWORD -e MYSQL_PASSWORD_FILE=/var/run/secrets/MYSQL_PASSWORD --init -d zabbix/zabbix-server-mysql:tag
+
podman run \
+    --name some-zabbix-server-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -v ./.MYSQL_USER:/run/secrets/MYSQL_USER \
+    -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER \
+    -v ./.MYSQL_PASSWORD:/run/secrets/MYSQL_PASSWORD \
+    -e MYSQL_PASSWORD_FILE=/var/run/secrets/MYSQL_PASSWORD \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-server-mysql-74:tag
 

 
With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!

-
printf "zabbix" | podman secret create MYSQL_USER -
-printf "zabbix" | podman secret create MYSQL_PASSWORD -
-podman run --name some-zabbix-server-mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER -e MYSQL_PASSWORD_FILE=/run/secrets/MYSQL_PASSWORD --init -d zabbix/zabbix-server-mysql:tag
+
printf "zabbix" | podman secret create MYSQL_USER -
+printf "zabbix" | podman secret create MYSQL_PASSWORD -
+podman run \
+    --name some-zabbix-server-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER \
+    -e MYSQL_PASSWORD_FILE=/run/secrets/MYSQL_PASSWORD \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-server-mysql-74:tag
 

 
This method is also applicable for MYSQL_ROOT_PASSWORD with MYSQL_ROOT_PASSWORD_FILE.

 
By default, values for MYSQL_USER and MYSQL_PASSWORD are zabbix, zabbix.

-
MYSQL_DATABASE

+
MYSQL_DATABASE

 
The variable is Zabbix database name. By default, value is zabbix.

-
ZBX_LOADMODULE

+
ZBX_LOADMODULE

 
The variable is list of comma separated loadable Zabbix modules. It works with  volume /var/lib/zabbix/modules. The syntax of the variable is dummy1.so,dummy2.so.

-
ZBX_DEBUGLEVEL

+
ZBX_DEBUGLEVEL

 
The variable is used to specify debug level. By default, value is 3. It is DebugLevel parameter in zabbix_server.conf. Allowed values are listed below:

 
    
 
  • 0 - basic information about starting and stopping of Zabbix processes;
    • 
@@ -69,146 +89,148 @@ podman run --name some-zabbix-server-mysql -e DB_SER
 
  • 4 - for debugging (produces lots of information)
    • 
 
  • 5 - extended debugging (produces even more information)
    • 
 

-
ZBX_TIMEOUT

+
ZBX_TIMEOUT

 
The variable is used to specify timeout for processing checks. By default, value is 4.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_ALLOWUNSUPPORTEDDBVERSIONS=0 # Available since 6.0.0
-ZBX_DBTLSCONNECT= # Available since 5.0.0
-ZBX_DBTLSCAFILE= # Available since 5.0.0
-ZBX_DBTLSCERTFILE= # Available since 5.0.0
-ZBX_DBTLSKEYFILE= # Available since 5.0.0
-ZBX_DBTLSCIPHER= # Available since 5.0.0
-ZBX_DBTLSCIPHER13= # Available since 5.0.0
-ZBX_VAULTPREFIX= # Available since 7.0.0
-ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
-ZBX_VAULTDBPATH= # Available since 5.2.0
-ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
-VAULT_TOKEN= # Available since 5.2.0
-ZBX_VAULTTLSCERTFILE= # Available since 6.2.0
-ZBX_VAULTTLSKEYFILE= # Available since 6.2.0
-ZBX_LISTENIP=
-ZBX_LISTENPORT=10051
-ZBX_LISTENBACKLOG=
-ZBX_STARTREPORTWRITERS=0 # Available since 5.4.0
-ZBX_WEBSERVICEURL=http://zabbix-web-service:10053/report # Available since 5.4.0
-ZBX_SERVICEMANAGERSYNCFREQUENCY=60 # Available since 6.0.0
-ZBX_HISTORYSTORAGEURL= # Available since 3.4.0
-ZBX_HISTORYSTORAGETYPES=uint,dbl,str,log,text # Available since 3.4.0
-ZBX_ENABLEGLOBALSCRIPTS=0 # Available since  7.0.0
-ZBX_STARTPOLLERS=5
-ZBX_MAXCONCURRENTCHECKSPERPOLLER=1000 # Available since 7.0.0
-ZBX_STARTAGENTPOLLERS=1 # Available since 7.0.0
-ZBX_STARTHTTPAGENTPOLLERS=1 # Available since 7.0.0
-ZBX_STARTIPMIPOLLERS=0
-ZBX_STARTPREPROCESSORS=16 # Available since 3.4.0
-ZBX_STARTCONNECTORS=0 # Available since 6.4.0
-ZBX_STARTPOLLERSUNREACHABLE=1
-ZBX_STARTTRAPPERS=5
-ZBX_STARTPINGERS=1
-ZBX_STARTDISCOVERERS=5
-ZBX_STARTHISTORYPOLLERS=5 # Available since 5.4.0
-ZBX_STARTHTTPPOLLERS=1
-ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
-ZBX_STARTTIMERS=1
-ZBX_STARTESCALATORS=1
-ZBX_STARTALERTERS=3 # Available since 3.4.0
-ZBX_JAVAGATEWAY=zabbix-java-gateway
-ZBX_JAVAGATEWAYPORT=10052
-ZBX_STARTJAVAPOLLERS=5
-ZBX_STARTLLDPROCESSORS=2 # Available since 4.2.0
-ZBX_STATSALLOWEDIP= # Available since 4.0.5
-ZBX_STARTVMWARECOLLECTORS=0
-ZBX_VMWAREFREQUENCY=60
-ZBX_VMWAREPERFFREQUENCY=60
-ZBX_VMWARECACHESIZE=8M
-ZBX_VMWARETIMEOUT=10
-ZBX_ENABLE_SNMP_TRAPS=false
-ZBX_SOURCEIP=
-ZBX_SMSDEVICES=
-ZBX_HOUSEKEEPINGFREQUENCY=1
-ZBX_MAXHOUSEKEEPERDELETE=5000
-ZBX_PROBLEMHOUSEKEEPINGFREQUENCY=60 # Available since 6.0.0
-ZBX_CACHESIZE=32M
-ZBX_CACHEUPDATEFREQUENCY=10
-ZBX_STARTDBSYNCERS=4
-ZBX_EXPORTFILESIZE=1G # Available since 4.0.0
-ZBX_EXPORTTYPE= # Available since 5.0.10 and 5.2.6
-ZBX_AUTOHANODENAME=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
-ZBX_HANODENAME= # Available since 6.0.0
-ZBX_AUTONODEADDRESS=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
-ZBX_NODEADDRESSPORT=10051 # Allowed to use with ZBX_AUTONODEADDRESS variable only. Available since 6.0.0
-ZBX_NODEADDRESS=localhost # Available since 6.0.0
-ZBX_HISTORYCACHESIZE=16M
-ZBX_HISTORYINDEXCACHESIZE=4M
-ZBX_HISTORYSTORAGEDATEINDEX=0 # Available since 4.0.0
-ZBX_TRENDCACHESIZE=4M
-ZBX_TRENDFUNCTIONCACHESIZE=4M
-ZBX_VALUECACHESIZE=8M
-ZBX_TRAPPERTIMEOUT=300
-ZBX_UNREACHABLEPERIOD=45
-ZBX_UNAVAILABLEDELAY=60
-ZBX_UNREACHABLEDELAY=15
-ZBX_LOGSLOWQUERIES=3000
-ZBX_STARTPROXYPOLLERS=1
-ZBX_PROXYCONFIGFREQUENCY=10
-ZBX_PROXYDATAFREQUENCY=1
-ZBX_TLSLISTEN= # Available since 7.4.0
-ZBX_TLSCAFILE=
-ZBX_TLSCA=
-ZBX_TLSCRLFILE=
-ZBX_TLSCRL=
-ZBX_TLSCERTFILE=
-ZBX_TLSCERT=
-ZBX_TLSKEYFILE=
-ZBX_TLSKEY=
-ZBX_TLSCIPHERALL= # Available since 4.4.7
-ZBX_TLSCIPHERALL13= # Available since 4.4.7
-ZBX_TLSCIPHERCERT= # Available since 4.4.7
-ZBX_TLSCIPHERCERT13= # Available since 4.4.7
-ZBX_TLSCIPHERPSK= # Available since 4.4.7
-ZBX_TLSCIPHERPSK13= # Available since 4.4.7
-ZBX_TLS_FRONTENDACCEPT= # Available since 7.4.0
-ZBX_FRONTENDALLOWEDIP= # Available since 7.4.0
-ZBX_TLSFRONTENDCERTISSUER= # Available since 7.4.0
-ZBX_TLSFRONTENDCERTSUBJECT= # Available since 7.4.0
-ZBX_ALLOWSOFTWAREUPDATECHECK=1 # Available since 7.0.0
-ZBX_WEBDRIVERURL= # Available since 7.0.0
-ZBX_STARTBROWSERPOLLERS=1 # Available since 7.0.0
-ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
-
Default values of these variables are specified after equal sign.

+
ZBX_ALLOWUNSUPPORTEDDBVERSIONS=0 # Available since 6.0.0
+ZBX_DBTLSCONNECT= # Available since 5.0.0
+ZBX_DBTLSCAFILE= # Available since 5.0.0
+ZBX_DBTLSCERTFILE= # Available since 5.0.0
+ZBX_DBTLSKEYFILE= # Available since 5.0.0
+ZBX_DBTLSCIPHER= # Available since 5.0.0
+ZBX_DBTLSCIPHER13= # Available since 5.0.0
+ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
+ZBX_VAULTDBPATH= # Available since 5.2.0
+ZBX_VAULTPREFIX= # Available since 7.0.0
+ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
+VAULT_TOKEN= # Available since 5.2.0
+ZBX_VAULTTLSCERTFILE= # Available since 6.2.0
+ZBX_VAULTTLSKEYFILE= # Available since 6.2.0
+ZBX_LISTENIP=
+ZBX_LISTENPORT=10051
+ZBX_LISTENBACKLOG=
+ZBX_STARTREPORTWRITERS=0 # Available since 5.4.0
+ZBX_WEBSERVICEURL=http://zabbix-web-service:10053/report # Available since 5.4.0
+ZBX_SERVICEMANAGERSYNCFREQUENCY=60 # Available since 6.0.0
+ZBX_HISTORYSTORAGEURL= # Available since 3.4.0
+ZBX_HISTORYSTORAGETYPES=uint,dbl,str,log,text # Available since 3.4.0
+ZBX_ENABLEGLOBALSCRIPTS=0 # Available since 7.0.0
+ZBX_ALLOWSOFTWAREUPDATECHECK=1 # Available since 7.0.0
+ZBX_MAXCONCURRENTCHECKSPERPOLLER=1000 # Available since 7.0.0
+ZBX_STARTAGENTPOLLERS=1 # Available since 7.0.0
+ZBX_STARTHTTPAGENTPOLLERS=1 # Available since 7.0.0
+ZBX_STARTPOLLERS=5
+ZBX_STARTIPMIPOLLERS=0
+ZBX_STARTPREPROCESSORS=16 # Available since 3.4.0
+ZBX_STARTCONNECTORS=0 # Available since 6.4.0
+ZBX_STARTPOLLERSUNREACHABLE=1
+ZBX_STARTTRAPPERS=5
+ZBX_STARTPINGERS=1
+ZBX_STARTDISCOVERERS=5
+ZBX_STARTHISTORYPOLLERS=5 # Available since 5.4.0
+ZBX_STARTHTTPPOLLERS=1
+ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
+ZBX_STARTTIMERS=1
+ZBX_STARTESCALATORS=1
+ZBX_STARTALERTERS=3 # Available since 3.4.0
+ZBX_JAVAGATEWAY=zabbix-java-gateway
+ZBX_JAVAGATEWAYPORT=10052
+ZBX_STARTJAVAPOLLERS=5
+ZBX_STARTLLDPROCESSORS=2 # Available since 4.2.0
+ZBX_STATSALLOWEDIP= # Available since 4.0.5
+ZBX_STARTVMWARECOLLECTORS=0
+ZBX_VMWAREFREQUENCY=60
+ZBX_VMWAREPERFFREQUENCY=60
+ZBX_VMWARECACHESIZE=8M
+ZBX_VMWARETIMEOUT=10
+ZBX_ENABLE_SNMP_TRAPS=false
+ZBX_SOURCEIP=
+ZBX_SMSDEVICES=
+ZBX_HOUSEKEEPINGFREQUENCY=1
+ZBX_MAXHOUSEKEEPERDELETE=5000
+ZBX_PROBLEMHOUSEKEEPINGFREQUENCY=60 # Available since 6.0.0
+ZBX_CACHESIZE=32M
+ZBX_CACHEUPDATEFREQUENCY=10
+ZBX_STARTDBSYNCERS=4
+ZBX_EXPORTFILESIZE=1G # Available since 4.0.0
+ZBX_EXPORTTYPE= # Available since 5.0.10 and 5.2.6
+ZBX_AUTOHANODENAME=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
+ZBX_HANODENAME= # Available since 6.0.0
+ZBX_AUTONODEADDRESS=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
+ZBX_NODEADDRESSPORT=10051 # Allowed to use with ZBX_AUTONODEADDRESS variable only. Available since 6.0.0
+ZBX_NODEADDRESS=localhost # Available since 6.0.0
+ZBX_HISTORYCACHESIZE=16M
+ZBX_HISTORYINDEXCACHESIZE=4M
+ZBX_HISTORYSTORAGEDATEINDEX=0 # Available since 4.0.0
+ZBX_TRENDCACHESIZE=4M
+ZBX_TRENDFUNCTIONCACHESIZE=4M
+ZBX_VALUECACHESIZE=8M
+ZBX_TRAPPERTIMEOUT=300
+ZBX_UNREACHABLEPERIOD=45
+ZBX_UNAVAILABLEDELAY=60
+ZBX_UNREACHABLEDELAY=15
+ZBX_LOGSLOWQUERIES=3000
+ZBX_STARTPROXYPOLLERS=1
+ZBX_PROXYCONFIGFREQUENCY=10
+ZBX_PROXYDATAFREQUENCY=1
+ZBX_TLSLISTEN= # Available since 7.4.0
+ZBX_TLSCAFILE=
+ZBX_TLSCA=
+ZBX_TLSCRLFILE=
+ZBX_TLSCRL=
+ZBX_TLSCERTFILE=
+ZBX_TLSCERT=
+ZBX_TLSKEYFILE=
+ZBX_TLSKEY=
+ZBX_TLSCIPHERALL= # Available since 4.4.7
+ZBX_TLSCIPHERALL13= # Available since 4.4.7
+ZBX_TLSCIPHERCERT= # Available since 4.4.7
+ZBX_TLSCIPHERCERT13= # Available since 4.4.7
+ZBX_TLSCIPHERPSK= # Available since 4.4.7
+ZBX_TLSCIPHERPSK13= # Available since 4.4.7
+ZBX_TLS_FRONTENDACCEPT= # Available since 7.4.0
+ZBX_FRONTENDALLOWEDIP= # Available since 7.4.0
+ZBX_TLSFRONTENDCERTISSUER= # Available since 7.4.0
+ZBX_TLSFRONTENDCERTSUBJECT= # Available since 7.4.0
+ZBX_WEBDRIVERURL= # Available since 7.0.0
+ZBX_STARTBROWSERPOLLERS=1 # Available since 7.0.0
+ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
+
+

+
Default values of these variables are specified after equal sign.

 
The allowed variables are identical of parameters in official zabbix_server.conf. For example, ZBX_LOGSLOWQUERIES = LogSlowQueries.

 
Please use official documentation for zabbix_server.conf to get more information about the variables.

-
Allowed volumes for the Zabbix server container

-
/usr/lib/zabbix/alertscripts

+
Allowed volumes for the Zabbix server container

+
/usr/lib/zabbix/alertscripts

 
The volume is used for custom alert scripts. It is AlertScriptsPath parameter in zabbix_server.conf.

-
/usr/lib/zabbix/externalscripts

+
/usr/lib/zabbix/externalscripts

 
The volume is used by External checks (type of items). It is ExternalScripts parameter in zabbix_server.conf.

-
/var/lib/zabbix/modules

+
/var/lib/zabbix/modules

 
The volume allows load additional modules and extend Zabbix server using LoadModule feature.

-
/var/lib/zabbix/enc

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_TLSCAFILE, ZBX_TLSCRLFILE, ZBX_TLSCERTFILE and ZBX_TLSKEYFILE variables. Additionally it is possible to use environment variables ZBX_TLSCA, ZBX_TLSCRL, ZBX_TLSCERT and ZBX_TLSKEY with plaintext values.

-
/var/lib/zabbix/ssh_keys

+
/var/lib/zabbix/ssh_keys

 
The volume is used as location of public and private keys for SSH checks and actions. It is SSHKeyLocation parameter in zabbix_server.conf.

-
/var/lib/zabbix/ssl/certs

-
The volume is used as location of of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_server.conf.

-
/var/lib/zabbix/ssl/keys

+
/var/lib/zabbix/ssl/certs

+
The volume is used as location of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_server.conf.

+
/var/lib/zabbix/ssl/keys

 
The volume is used as location of SSL private key files for client authentication. It is SSLKeyLocation parameter in zabbix_server.conf.

-
/var/lib/zabbix/ssl/ssl_ca

+
/var/lib/zabbix/ssl/ssl_ca

 
The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is SSLCALocation parameter in zabbix_server.conf.

-
/var/lib/zabbix/snmptraps

+
/var/lib/zabbix/snmptraps

 
The volume is used as location of snmptraps.log file. It could be shared by zabbix-snmptraps container and inherited using volumes_from Podman option while creating new instance of Zabbix server.
 SNMP traps processing feature could be enabled using shared volume and switched ZBX_ENABLE_SNMP_TRAPS environment variable to true.

-
/var/lib/zabbix/mibs

-
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed to /var/lib/zabbix/mibs.

-
/var/lib/zabbix/export

+
/var/lib/zabbix/mibs

+
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in /var/lib/zabbix/mibs.

+
/var/lib/zabbix/export

 
Directory for real-time export of events, history and trends in newline-delimited JSON format. Could be enabled using ZBX_EXPORTFILESIZE environment variable.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the server-mysql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the server-mysql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

-
Contributing

+
Known issues

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/server-pgsql/rhel/README.html b/Dockerfiles/server-pgsql/rhel/README.html
index 49379613..d15b6f9c 100644
--- a/Dockerfiles/server-pgsql/rhel/README.html
+++ b/Dockerfiles/server-pgsql/rhel/README.html
@@ -1,12 +1,11 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix server?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix server?

 
Zabbix server is the central process of Zabbix software.

 
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.

-
Zabbix server images

+
Zabbix server images

 
Images are updated when new releases are published.

 
The image uses PostgreSQL database. It uses the next procedure to start:

 
    
@@ -14,201 +13,225 @@
 
  • Checking of having POSTGRES_DB database. Creating POSTGRES_DB database name if it does not exist
    • 
 
  • Checking of having dbversion table. Creating Zabbix server database schema and upload initial data sample if no dbversion table
    • 
 

-
How to use this image

-
Start zabbix-server-pgsql

+
How to use this image

+
Start zabbix-server-pgsql

 
Start a Zabbix server container as follows:

-
podman run --name some-zabbix-server-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -d zabbix/zabbix-server-pgsql:tag
-
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.

+
podman run \
+    --name some-zabbix-server-pgsql \
+    -e DB_SERVER_HOST="some-postgres-server" \
+    -e POSTGRES_USER="some-user" \
+    -e POSTGRES_PASSWORD="some-password" \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-server-pgsql-74:tag
+

+
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.

 

-
[!NOTE]
+
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 podman run or podman run commands.
+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

+
Container shell access and viewing Zabbix server logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-server-pgsql container:

-
$ podman exec -ti some-zabbix-server-pgsql /bin/bash
+
$ podman exec -ti some-zabbix-server-pgsql /bin/bash
 

-
The Zabbix server log is available through Podman's container log:

-
$ podman logs some-zabbix-server-pgsql
+
The Zabbix server log is available through Podman's container log:

+
$ podman logs some-zabbix-server-pgsql
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-server-pgsql image, you can adjust the configuration of the Zabbix server by passing one or more environment variables on the podman run command line.

-
DB_SERVER_HOST

-
This variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'

-
DB_SERVER_PORT

-
This variable is port of PostgreSQL server. By default, value is '5432'.

-
POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_USER_FILE, POSTGRES_PASSWORD_FILE

+
DB_SERVER_HOST

+
This variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'

+
DB_SERVER_PORT

+
This variable is port of PostgreSQL server. By default, value is '5432'.

+
POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_USER_FILE, POSTGRES_PASSWORD_FILE

 
These variables are used by Zabbix server to connect to Zabbix database. With the _FILE 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 POSTGRES_USER or POSTGRES_USER_FILE!

-
podman run --name some-zabbix-server-pgsql -e DB_SERVER_HOST="some-postgres-server" -v ./.POSTGRES_USER:/run/secrets/POSTGRES_USER -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -v ./.POSTGRES_PASSWORD:/run/secrets/POSTGRES_PASSWORD -e POSTGRES_PASSWORD_FILE=/var/run/secrets/POSTGRES_PASSWORD -d zabbix/zabbix-server-pgsql:tag
+
podman run \
+    --name some-zabbix-server-pgsql \
+    -e DB_SERVER_HOST="some-postgres-server" \
+    -v ./.POSTGRES_USER:/run/secrets/POSTGRES_USER \
+    -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER \
+    -v ./.POSTGRES_PASSWORD:/run/secrets/POSTGRES_PASSWORD \
+    -e POSTGRES_PASSWORD_FILE=/var/run/secrets/POSTGRES_PASSWORD \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-server-pgsql-74:tag
 

 
With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!

-
printf "zabbix" | podman secret create POSTGRES_USER -
-printf "zabbix" | podman secret create POSTGRES_PASSWORD -
-podman run --name some-zabbix-server-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -e POSTGRES_PASSWORD_FILE=/run/secrets/POSTGRES_PASSWORD -d zabbix/zabbix-server-pgsql:tag
+
printf "zabbix" | podman secret create POSTGRES_USER -
+printf "zabbix" | podman secret create POSTGRES_PASSWORD -
+podman run \
+    --name some-zabbix-server-pgsql \
+    -e DB_SERVER_HOST="some-postgres-server" \
+    -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER \
+    -e POSTGRES_PASSWORD_FILE=/run/secrets/POSTGRES_PASSWORD \
+    --init \
+    -d registry.connect.redhat.com/zabbix/zabbix-server-pgsql-74:tag
 

 
By default, values for POSTGRES_USER and POSTGRES_PASSWORD are zabbix, zabbix.

-
POSTGRES_DB

+
POSTGRES_DB

 
The variable is Zabbix database name. By default, value is zabbix.

-
POSTGRES_USE_IMPLICIT_SEARCH_PATH

-
In some setups, for example including PgBouncer, setting the search_path via connection parameters fails. If this variable is set to "true", the image skips setting the search_path and trusts that the search_path of the Zabbix user is setup correctly in PostgreSQL database.

-
ZBX_LOADMODULE

+
POSTGRES_USE_IMPLICIT_SEARCH_PATH

+
In some setups, for example including PgBouncer, setting the search_path via connection parameters fails. If this variable is set to "true", the image skips setting the search_path and trusts that the search_path of the Zabbix user is setup correctly in PostgreSQL database.

+
ZBX_LOADMODULE

 
The variable is list of comma separated loadable Zabbix modules. It works with  volume /var/lib/zabbix/modules. The syntax of the variable is dummy1.so,dummy2.so.

-
ZBX_DEBUGLEVEL

+
ZBX_DEBUGLEVEL

 
The variable is used to specify debug level. By default, value is 3. It is DebugLevel parameter in zabbix_server.conf. Allowed values are listed below:

 
    
 
  • 0 - basic information about starting and stopping of Zabbix processes;
    • 
 
  • 1 - critical information
    • 
 
  • 2 - error information
    • 
 
  • 3 - warnings
    • 
-
  • 4 - for debugging (produces lots of information)
    • 
+
  • 4 -  for debugging (produces lots of information)
    • 
 
  • 5 - extended debugging (produces even more information)
    • 
 

-
ZBX_TIMEOUT

+
ZBX_TIMEOUT

 
The variable is used to specify timeout for processing checks. By default, value is 4.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_ALLOWUNSUPPORTEDDBVERSIONS=0 # Available since 6.0.0
-ZBX_DBTLSCONNECT= # Available since 5.0.0
-ZBX_DBTLSCAFILE= # Available since 5.0.0
-ZBX_DBTLSCERTFILE= # Available since 5.0.0
-ZBX_DBTLSKEYFILE= # Available since 5.0.0
-ZBX_DBTLSCIPHER= # Available since 5.0.0
-ZBX_DBTLSCIPHER13= # Available since 5.0.0
-ZBX_VAULTPREFIX= # Available since 7.0.0
-ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
-ZBX_VAULTDBPATH= # Available since 5.2.0
-ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
-VAULT_TOKEN= # Available since 5.2.0
-ZBX_VAULTTLSCERTFILE= # Available since 6.2.0
-ZBX_VAULTTLSKEYFILE= # Available since 6.2.0
-ZBX_LISTENIP=
-ZBX_LISTENPORT=10051
-ZBX_LISTENBACKLOG=
-ZBX_STARTREPORTWRITERS=0 # Available since 5.4.0
-ZBX_WEBSERVICEURL=http://zabbix-web-service:10053/report # Available since 5.4.0
-ZBX_SERVICEMANAGERSYNCFREQUENCY=60 # Available since 6.0.0
-ZBX_HISTORYSTORAGEURL= # Available since 3.4.0
-ZBX_HISTORYSTORAGETYPES=uint,dbl,str,log,text # Available since 3.4.0
-ZBX_ENABLEGLOBALSCRIPTS=0 # Available since  7.0
-ZBX_STARTPOLLERS=5
-ZBX_MAXCONCURRENTCHECKSPERPOLLER=1000 # Available since 7.0.0
-ZBX_STARTAGENTPOLLERS=1 # Available since 7.0.0
-ZBX_STARTHTTPAGENTPOLLERS=1 # Available since 7.0.0
-ZBX_STARTIPMIPOLLERS=0
-ZBX_STARTCONNECTORS=0 # Available since 6.4.0
-ZBX_STARTPREPROCESSORS=16 # Available since 3.4.0
-ZBX_STARTPOLLERSUNREACHABLE=1
-ZBX_STARTTRAPPERS=5
-ZBX_STARTPINGERS=1
-ZBX_STARTDISCOVERERS=5
-ZBX_STARTHISTORYPOLLERS=5 # Available since 5.4.0
-ZBX_STARTHTTPPOLLERS=1
-ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
-ZBX_STARTTIMERS=1
-ZBX_STARTESCALATORS=1
-ZBX_STARTALERTERS=3 # Available since 3.4.0
-ZBX_JAVAGATEWAY=zabbix-java-gateway
-ZBX_JAVAGATEWAYPORT=10052
-ZBX_STARTJAVAPOLLERS=5
-ZBX_STARTLLDPROCESSORS=2 # Available since 4.2.0
-ZBX_STATSALLOWEDIP= # Available since 4.0.5
-ZBX_STARTVMWARECOLLECTORS=0
-ZBX_VMWAREFREQUENCY=60
-ZBX_VMWAREPERFFREQUENCY=60
-ZBX_VMWARECACHESIZE=8M
-ZBX_VMWARETIMEOUT=10
-ZBX_ENABLE_SNMP_TRAPS=false
-ZBX_SMSDEVICES=
-ZBX_SOURCEIP=
-ZBX_HOUSEKEEPINGFREQUENCY=1
-ZBX_MAXHOUSEKEEPERDELETE=5000
-ZBX_PROBLEMHOUSEKEEPINGFREQUENCY=60 # Available since 6.0.0
-ZBX_CACHESIZE=32M
-ZBX_CACHEUPDATEFREQUENCY=10
-ZBX_STARTDBSYNCERS=4
-ZBX_EXPORTFILESIZE=1G # Available since 4.0.0
-ZBX_EXPORTTYPE= # Available since 5.0.10 and 5.2.6
-ZBX_AUTOHANODENAME=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
-ZBX_HANODENAME= # Available since 6.0.0
-ZBX_AUTONODEADDRESS=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
-ZBX_NODEADDRESSPORT=10051 # Allowed to use with ZBX_AUTONODEADDRESS variable only. Available since 6.0.0
-ZBX_NODEADDRESS=localhost # Available since 6.0.0
-ZBX_HISTORYCACHESIZE=16M
-ZBX_HISTORYINDEXCACHESIZE=4M
-ZBX_HISTORYSTORAGEDATEINDEX=0 # Available since 4.0.0
-ZBX_TRENDCACHESIZE=4M
-ZBX_TRENDFUNCTIONCACHESIZE=4M
-ZBX_VALUECACHESIZE=8M
-ZBX_TRAPPERTIMEOUT=300
-ZBX_UNREACHABLEPERIOD=45
-ZBX_UNAVAILABLEDELAY=60
-ZBX_UNREACHABLEDELAY=15
-ZBX_LOGSLOWQUERIES=3000
-ZBX_STARTPROXYPOLLERS=1
-ZBX_PROXYCONFIGFREQUENCY=10
-ZBX_PROXYDATAFREQUENCY=1
-ZBX_TLSLISTEN= # Available since 7.4.0
-ZBX_TLSCAFILE=
-ZBX_TLSCA=
-ZBX_TLSCRLFILE=
-ZBX_TLSCRL=
-ZBX_TLSCERTFILE=
-ZBX_TLSCERT=
-ZBX_TLSKEYFILE=
-ZBX_TLSKEY=
-ZBX_TLSCIPHERALL= # Available since 4.4.7
-ZBX_TLSCIPHERALL13= # Available since 4.4.7
-ZBX_TLSCIPHERCERT= # Available since 4.4.7
-ZBX_TLSCIPHERCERT13= # Available since 4.4.7
-ZBX_TLSCIPHERPSK= # Available since 4.4.7
-ZBX_TLSCIPHERPSK13= # Available since 4.4.7
-ZBX_TLS_FRONTENDACCEPT= # Available since 7.4.0
-ZBX_FRONTENDALLOWEDIP= # Available since 7.4.0
-ZBX_TLSFRONTENDCERTISSUER= # Available since 7.4.0
-ZBX_TLSFRONTENDCERTSUBJECT= # Available since 7.4.0
-ZBX_ALLOWSOFTWAREUPDATECHECK=1 # Available since 7.0.0
-ZBX_WEBDRIVERURL= # Available since 7.0.0
-ZBX_STARTBROWSERPOLLERS=1 # Available since 7.0.0
-ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
-
Default values of these variables are specified after equal sign.

+
ZBX_ALLOWUNSUPPORTEDDBVERSIONS=0 # Available since 6.0.0
+ZBX_DBTLSCONNECT= # Available since 5.0.0
+ZBX_DBTLSCAFILE= # Available since 5.0.0
+ZBX_DBTLSCERTFILE= # Available since 5.0.0
+ZBX_DBTLSKEYFILE= # Available since 5.0.0
+ZBX_DBTLSCIPHER= # Available since 5.0.0
+ZBX_DBTLSCIPHER13= # Available since 5.0.0
+ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
+ZBX_VAULTDBPATH= # Available since 5.2.0
+ZBX_VAULTPREFIX= # Available since 7.0.0
+ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
+VAULT_TOKEN= # Available since 5.2.0
+ZBX_VAULTTLSCERTFILE= # Available since 6.2.0
+ZBX_VAULTTLSKEYFILE= # Available since 6.2.0
+ZBX_LISTENIP=
+ZBX_LISTENPORT=10051
+ZBX_LISTENBACKLOG=
+ZBX_STARTREPORTWRITERS=0 # Available since 5.4.0
+ZBX_WEBSERVICEURL=http://zabbix-web-service:10053/report # Available since 5.4.0
+ZBX_SERVICEMANAGERSYNCFREQUENCY=60 # Available since 6.0.0
+ZBX_HISTORYSTORAGEURL= # Available since 3.4.0
+ZBX_HISTORYSTORAGETYPES=uint,dbl,str,log,text # Available since 3.4.0
+ZBX_ENABLEGLOBALSCRIPTS=0 # Available since 7.0.0
+ZBX_ALLOWSOFTWAREUPDATECHECK=1 # Available since 7.0.0
+ZBX_MAXCONCURRENTCHECKSPERPOLLER=1000 # Available since 7.0.0
+ZBX_STARTAGENTPOLLERS=1 # Available since 7.0.0
+ZBX_STARTHTTPAGENTPOLLERS=1 # Available since 7.0.0
+ZBX_STARTPOLLERS=5
+ZBX_STARTIPMIPOLLERS=0
+ZBX_STARTCONNECTORS=0 # Available since 6.4.0
+ZBX_STARTPREPROCESSORS=16 # Available since 3.4.0
+ZBX_STARTPOLLERSUNREACHABLE=1
+ZBX_STARTTRAPPERS=5
+ZBX_STARTPINGERS=1
+ZBX_STARTDISCOVERERS=5
+ZBX_STARTHISTORYPOLLERS=5 # Available since 5.4.0
+ZBX_STARTHTTPPOLLERS=1
+ZBX_STARTODBCPOLLERS=1 # Available since 6.0.0
+ZBX_STARTTIMERS=1
+ZBX_STARTESCALATORS=1
+ZBX_STARTALERTERS=3 # Available since 3.4.0
+ZBX_JAVAGATEWAY=zabbix-java-gateway
+ZBX_JAVAGATEWAYPORT=10052
+ZBX_STARTJAVAPOLLERS=5
+ZBX_STARTLLDPROCESSORS=2 # Available since 4.2.0
+ZBX_STATSALLOWEDIP= # Available since 4.0.5
+ZBX_STARTVMWARECOLLECTORS=0
+ZBX_VMWAREFREQUENCY=60
+ZBX_VMWAREPERFFREQUENCY=60
+ZBX_VMWARECACHESIZE=8M
+ZBX_VMWARETIMEOUT=10
+ZBX_ENABLE_SNMP_TRAPS=false
+ZBX_SOURCEIP=
+ZBX_SMSDEVICES=
+ZBX_HOUSEKEEPINGFREQUENCY=1
+ZBX_MAXHOUSEKEEPERDELETE=5000
+ZBX_PROBLEMHOUSEKEEPINGFREQUENCY=60 # Available since 6.0.0
+ZBX_CACHESIZE=32M
+ZBX_CACHEUPDATEFREQUENCY=10
+ZBX_STARTDBSYNCERS=4
+ZBX_EXPORTFILESIZE=1G # Available since 4.0.0
+ZBX_EXPORTTYPE= # Available since 5.0.10 and 5.2.6
+ZBX_AUTOHANODENAME=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
+ZBX_HANODENAME= # Available since 6.0.0
+ZBX_AUTONODEADDRESS=fqdn # Allowed values: fqdn, hostname. Available since 6.0.0
+ZBX_NODEADDRESSPORT=10051 # Allowed to use with ZBX_AUTONODEADDRESS variable only. Available since 6.0.0
+ZBX_NODEADDRESS=localhost # Available since 6.0.0
+ZBX_HISTORYCACHESIZE=16M
+ZBX_HISTORYINDEXCACHESIZE=4M
+ZBX_HISTORYSTORAGEDATEINDEX=0 # Available since 4.0.0
+ZBX_TRENDCACHESIZE=4M
+ZBX_TRENDFUNCTIONCACHESIZE=4M
+ZBX_VALUECACHESIZE=8M
+ZBX_TRAPPERTIMEOUT=300
+ZBX_UNREACHABLEPERIOD=45
+ZBX_UNAVAILABLEDELAY=60
+ZBX_UNREACHABLEDELAY=15
+ZBX_LOGSLOWQUERIES=3000
+ZBX_STARTPROXYPOLLERS=1
+ZBX_PROXYCONFIGFREQUENCY=10
+ZBX_PROXYDATAFREQUENCY=1
+ZBX_TLSLISTEN= # Available since 7.4.0
+ZBX_TLSCAFILE=
+ZBX_TLSCA=
+ZBX_TLSCRLFILE=
+ZBX_TLSCRL=
+ZBX_TLSCERTFILE=
+ZBX_TLSCERT=
+ZBX_TLSKEYFILE=
+ZBX_TLSKEY=
+ZBX_TLSCIPHERALL= # Available since 4.4.7
+ZBX_TLSCIPHERALL13= # Available since 4.4.7
+ZBX_TLSCIPHERCERT= # Available since 4.4.7
+ZBX_TLSCIPHERCERT13= # Available since 4.4.7
+ZBX_TLSCIPHERPSK= # Available since 4.4.7
+ZBX_TLSCIPHERPSK13= # Available since 4.4.7
+ZBX_TLS_FRONTENDACCEPT= # Available since 7.4.0
+ZBX_FRONTENDALLOWEDIP= # Available since 7.4.0
+ZBX_TLSFRONTENDCERTISSUER= # Available since 7.4.0
+ZBX_TLSFRONTENDCERTSUBJECT= # Available since 7.4.0
+ZBX_WEBDRIVERURL= # Available since 7.0.0
+ZBX_STARTBROWSERPOLLERS=1 # Available since 7.0.0
+ZBX_STARTSNMPPOLLERS=1 # Available since 7.0.0
+
+

+
Default values of these variables are specified after equal sign.

 
The allowed variables are identical of parameters in official zabbix_server.conf. For example, ZBX_LOGSLOWQUERIES = LogSlowQueries.

 
Please use official documentation for zabbix_server.conf to get more information about the variables.

-
Allowed volumes for the Zabbix server container

-
/usr/lib/zabbix/alertscripts

+
Allowed volumes for the Zabbix server container

+
/usr/lib/zabbix/alertscripts

 
The volume is used for custom alert scripts. It is AlertScriptsPath parameter in zabbix_server.conf.

-
/usr/lib/zabbix/externalscripts

+
/usr/lib/zabbix/externalscripts

 
The volume is used by External checks (type of items). It is ExternalScripts parameter in zabbix_server.conf.

-
/var/lib/zabbix/modules

+
/var/lib/zabbix/modules

 
The volume allows load additional modules and extend Zabbix server using LoadModule feature.

-
/var/lib/zabbix/enc

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_TLSCAFILE, ZBX_TLSCRLFILE, ZBX_TLSCERTFILE and ZBX_TLSKEYFILE variables. Additionally it is possible to use environment variables ZBX_TLSCA, ZBX_TLSCRL, ZBX_TLSCERT and ZBX_TLSKEY with plaintext values.

-
/var/lib/zabbix/ssh_keys

+
/var/lib/zabbix/ssh_keys

 
The volume is used as location of public and private keys for SSH checks and actions. It is SSHKeyLocation parameter in zabbix_server.conf.

-
/var/lib/zabbix/ssl/certs

-
The volume is used as location of of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_server.conf.

-
/var/lib/zabbix/ssl/keys

+
/var/lib/zabbix/ssl/certs

+
The volume is used as location of SSL client certificate files for client authentication. It is SSLCertLocation parameter in zabbix_server.conf.

+
/var/lib/zabbix/ssl/keys

 
The volume is used as location of SSL private key files for client authentication. It is SSLKeyLocation parameter in zabbix_server.conf.

-
/var/lib/zabbix/ssl/ssl_ca

+
/var/lib/zabbix/ssl/ssl_ca

 
The volume is used as location of certificate authority (CA) files for SSL server certificate verification. It is SSLCALocation parameter in zabbix_server.conf.

-
/var/lib/zabbix/snmptraps

+
/var/lib/zabbix/snmptraps

 
The volume is used as location of snmptraps.log file. It could be shared by zabbix-snmptraps container and inherited using volumes_from Podman option while creating new instance of Zabbix server.
 SNMP traps processing feature could be enabled using shared volume and switched ZBX_ENABLE_SNMP_TRAPS environment variable to true.

-
/var/lib/zabbix/mibs

-
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed to /var/lib/zabbix/mibs.

-
/var/lib/zabbix/export

+
/var/lib/zabbix/mibs

+
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in /var/lib/zabbix/mibs.

+
/var/lib/zabbix/export

 
Directory for real-time export of events, history and trends in newline-delimited JSON format. Could be enabled using ZBX_EXPORTFILESIZE environment variable.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the server-pgsql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the server-pgsql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

-
Contributing

+
Known issues

+
Zabbix server does not support Jabber notifications on Alpine Linux because of iksemel package is in testing repository and not available in stable repository.

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/snmptraps/rhel/README.html b/Dockerfiles/snmptraps/rhel/README.html
index 7010044f..01d333a2 100644
--- a/Dockerfiles/snmptraps/rhel/README.html
+++ b/Dockerfiles/snmptraps/rhel/README.html
@@ -1,47 +1,58 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is the image?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is the image?

 
The image is used to receive SNMP traps, store them to a log file and provide access to Zabbix to collected SNMP trap messsages.

-
Zabbix snmptraps images

-
These are the only official Zabbix snmptraps Podman images. Images are updated when new releases are published.

-
How to use this image

-
Start zabbix-snmptraps

+
Zabbix snmptraps images

+
Images are updated when new releases are published.

+
How to use this image

+
Start zabbix-snmptraps

 
Start a Zabbix snmptraps container as follows:

-
podman run --name some-zabbix-snmptraps -p 162:1162/udp -d zabbix/zabbix-snmptraps:tag
-
Where some-zabbix-snmptraps is the name you want to assign to your container 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.

-
Linking Zabbix server or Zabbix proxy with the container

-
podman run --name some-zabbix-server --link some-zabbix-snmptraps:zabbix-snmptraps --volumes-from some-zabbix-snmptraps -d zabbix/zabbix-server:tag
-
Container shell access and viewing Zabbix snmptraps logs

+
podman run \
+    --name some-zabbix-snmptraps \
+    -p 162:1162/udp \
+    -d registry.connect.redhat.com/zabbix/zabbix-snmptraps-74:tag
+

+
Where some-zabbix-snmptraps is the name you want to assign to your container and tag is the tag specifying the version you want.

+
Linking Zabbix server or Zabbix proxy with the container

+
podman run \
+    --name some-zabbix-server \
+    --link some-zabbix-snmptraps:zabbix-snmptraps \
+    --volumes-from some-zabbix-snmptraps \
+    -d zabbix/zabbix-server:tag
+

+
Container shell access and viewing Zabbix snmptraps logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-snmptraps container:

-
$ podman exec -ti some-zabbix-snmptraps /bin/bash
+
$ podman exec -ti some-zabbix-snmptraps /bin/bash
 

-
The Zabbix snmptraps log is available through Podman's container log:

-
$ podman logs  some-zabbix-snmptraps
+
The Zabbix snmptraps log is available through Podman's container log:

+
$ podman logs  some-zabbix-snmptraps
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-snmptraps image, you can adjust the configuration by passing one or more environment variables on the podman run command line.

-
ZBX_SNMP_TRAP_DATE_FORMAT

+
ZBX_SNMP_TRAP_DATE_FORMAT

 
This variable is represent date and time format in the output snmptraps.log file. By default, value is +%Y-%m-%dT%T%z. Please, refer to date command man for more details about date and time format.

-
ZBX_SNMP_TRAP_FORMAT

+
ZBX_SNMP_TRAP_FORMAT

 
This variable is SNMP trap format in the output snmptraps.log file. By default, value is \n, in this case each new variable is placed on new line.

-
ZBX_SNMP_TRAP_USE_DNS

-
This variable manages source network address representation. It can be IP address or DNS of SNMP trap sender. The variable works only when container command is modified and "-n" command argument is removed from argument list. By default, value is false.

-
Allowed volumes for the Zabbix snmptraps container

-
/var/lib/zabbix/snmptraps

+
ZBX_SNMP_TRAP_USE_DNS

+
This variable manages source network address representation. It can be IP address or DNS of SNMP trap sender. The variable works only when container command is modified and "-n" command argument is removed from argument list. By default, value is false.

+
SNMPTRAP_OUTPUT_OPTIONS

+
Modify standard output options for SNMP traps. By default, value is STte. Corresponding to "OUTPUT OPTIONS" ("-O" command line argument).

+
Allowed volumes for the Zabbix snmptraps container

+
/var/lib/zabbix/snmptraps

 
The volume contains log file snmptraps.log named with received SNMP traps.

-
/var/lib/zabbix/mibs

-
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed to /var/lib/zabbix/mibs.

-
/var/lib/zabbix/snmptrapd_config

+
/var/lib/zabbix/mibs

+
The volume allows to add new MIB files. It does not support subdirectories, all MIBs must be placed in /var/lib/zabbix/mibs.

+
/var/lib/zabbix/snmptrapd_config

 
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.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the snmptraps/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
The volume also can be used for custom configuration file snmptrapd_custom.conf. The configuration file can be used for SNMPv3 authentification details.

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the snmptraps/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

-
Contributing

+
Known issues

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/web-nginx-mysql/rhel/README.html b/Dockerfiles/web-nginx-mysql/rhel/README.html
index a5483838..3bf5770f 100644
--- a/Dockerfiles/web-nginx-mysql/rhel/README.html
+++ b/Dockerfiles/web-nginx-mysql/rhel/README.html
@@ -1,13 +1,12 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix web interface?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix web interface?

 
Zabbix web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics.

-
Zabbix web interface images

-
These are the only official Zabbix web interface Podman images. Images are updated when new releases are published.

-
Zabbix web interface available in four editions, but only one as Red Hat Certified container:

+
Zabbix web interface images

+
Images are updated when new releases are published.

+
Zabbix web interface available in four editions:

 
    
 
  • Zabbix web-interface based on Apache2 web server with MySQL database support
    • 
 
  • Zabbix web-interface based on Apache2 web server with PostgreSQL database support
    • 
@@ -15,153 +14,195 @@
 
  • Zabbix web-interface based on Nginx web server with PostgreSQL database support
    • 
 

 
The image based on Nginx web server with MySQL database support.

-
How to use this image

-
Start zabbix-web-nginx-mysql

+
How to use this image

+
Start zabbix-web-nginx-mysql

 
Start a Zabbix web-interface container as follows:

-
podman run --name some-zabbix-web-nginx-mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER="some-user" -e MYSQL_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag
-
Where some-zabbix-web-nginx-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-zabbix-server is IP or DNS name of Zabbix server or proxy, some-timezone is PHP like timezone name and tag is the tag specifying the version you want.

-
Linking the container to Zabbix server

-
podman run --name some-zabbix-web-nginx-mysql --link some-zabbix-server:zabbix-server -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER="some-user" -e MYSQL_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag
-
Linking the container to MySQL database

-
podman run --name some-zabbix-web-nginx-mysql --link some-mysql-server:mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER="some-user" -e MYSQL_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag
-
Container shell access and viewing Zabbix web interface logs

+
podman run \
+    --name some-zabbix-web-nginx-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -e MYSQL_USER="some-user" \
+    -e MYSQL_PASSWORD="some-password" \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-mysql-74:tag
+

+
Where some-zabbix-web-nginx-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-zabbix-server is IP or DNS name of Zabbix server or proxy, some-timezone is PHP like timezone name and tag is the tag specifying the version you want.

+
Linking the container to Zabbix server

+
podman run \
+    --name some-zabbix-web-nginx-mysql \
+    --link some-zabbix-server:zabbix-server \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -e MYSQL_USER="some-user" \
+    -e MYSQL_PASSWORD="some-password" \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-mysql-74:tag
+

+
Linking the container to MySQL database

+
podman run \
+    --name some-zabbix-web-nginx-mysql \
+    --link some-mysql-server:mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -e MYSQL_USER="some-user" \
+    -e MYSQL_PASSWORD="some-password" \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-mysql-74:tag
+

+
Container shell access and viewing Zabbix web interface logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-web-nginx-mysql container:

-
$ podman exec -ti some-zabbix-web-nginx-mysql /bin/bash
+
$ podman exec -ti some-zabbix-web-nginx-mysql /bin/bash
 

-
The Zabbix web interface log is available through Podman's container log:

-
$ podman logs  some-zabbix-web-nginx-mysql
+
The Zabbix web interface log is available through Podman's container log:

+
$ podman logs  some-zabbix-web-nginx-mysql
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-web-nginx-mysql image, you can adjust the configuration of the Zabbix web interface by passing one or more environment variables on the podman run command line.

-
ZBX_SERVER_HOST

+
ZBX_SERVER_HOST

 
This variable is IP or DNS name of Zabbix server. By default, value is zabbix-server.

-
ZBX_SERVER_PORT

+
ZBX_SERVER_PORT

 
This variable is port Zabbix server listening on. By default, value is 10051.

-
DB_SERVER_HOST

-
This variable is IP or DNS name of MySQL server. By default, value is 'mysql-server'

-
DB_SERVER_PORT

-
This variable is port of MySQL server. By default, value is '3306'.

-
MYSQL_USER, MYSQL_PASSWORD, MYSQL_USER_FILE, MYSQL_PASSWORD_FILE

+
DB_SERVER_HOST

+
This variable is IP or DNS name of MySQL server. By default, value is 'mysql-server'

+
DB_SERVER_PORT

+
This variable is port of MySQL server. By default, value is '3306'.

+
MYSQL_USER, MYSQL_PASSWORD, MYSQL_USER_FILE, MYSQL_PASSWORD_FILE

 
These variables are used by Zabbix web-interface to connect to Zabbix database. With the _FILE 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 MYSQL_USER or MYSQL_USER_FILE!

-
podman run --name some-zabbix-web-nginx-mysql -e DB_SERVER_HOST="some-mysql-server" -v ./.MYSQL_USER:/run/secrets/MYSQL_USER -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER -v ./.MYSQL_PASSWORD:/run/secrets/MYSQL_PASSWORD -e MYSQL_PASSWORD_FILE=/var/run/secrets/MYSQL_PASSWORD -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag
+
podman run \
+    --name some-zabbix-web-nginx-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -v ./.MYSQL_USER:/run/secrets/MYSQL_USER \
+    -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER \
+    -v ./.MYSQL_PASSWORD:/run/secrets/MYSQL_PASSWORD \
+    -e MYSQL_PASSWORD_FILE=/var/run/secrets/MYSQL_PASSWORD \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-mysql-74:tag
 

 
With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!

-
printf "zabbix" | podman secret create MYSQL_USER -
-printf "zabbix" | podman secret create MYSQL_PASSWORD -
-podman run --name some-zabbix-web-nginx-mysql -e DB_SERVER_HOST="some-mysql-server" -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER -e MYSQL_PASSWORD_FILE=/run/secrets/MYSQL_PASSWORD -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-mysql:tag
+
printf "zabbix" | podman secret create MYSQL_USER -
+printf "zabbix" | podman secret create MYSQL_PASSWORD -
+podman run \
+    --name some-zabbix-web-nginx-mysql \
+    -e DB_SERVER_HOST="some-mysql-server" \
+    -e MYSQL_USER_FILE=/run/secrets/MYSQL_USER \
+    -e MYSQL_PASSWORD_FILE=/run/secrets/MYSQL_PASSWORD \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-mysql-74:tag
 

 
By default, values for MYSQL_USER and MYSQL_PASSWORD are zabbix, zabbix.

-
MYSQL_DATABASE

+
MYSQL_DATABASE

 
The variable is Zabbix database name. By default, value is zabbix.

-
ZBX_HISTORYSTORAGEURL

+
ZBX_HISTORYSTORAGEURL

 
History storage HTTP[S] URL. This parameter is used for Elasticsearch setup. Available since 3.4.5.

-
ZBX_HISTORYSTORAGETYPES

-
Array of value types to be sent to the history storage. An example: ['uint', 'dbl']. This parameter is used for Elasticsearch setup. Available since 3.4.5.

-
PHP_TZ

-
The variable is timezone in PHP format. Full list of supported timezones are available on php.net. By default, value is 'Europe/Riga' and system timezone since Zabbix 5.2.0.

-
ZBX_SERVER_NAME

+
ZBX_HISTORYSTORAGETYPES

+
Array of value types to be sent to the history storage. An example: ['uint', 'dbl']. This parameter is used for Elasticsearch setup. Available since 3.4.5.

+
PHP_TZ

+
The variable is timezone in PHP format. Full list of supported timezones are available on php.net. By default, value is 'Europe/Riga' and system timezone since Zabbix 5.2.0.

+
ZBX_SERVER_NAME

 
The variable is visible Zabbix installation name in right or left top corner of the web interface.

-
DB_DOUBLE_IEEE754

+
DB_DOUBLE_IEEE754

 
Use IEEE754 compatible value range for 64-bit Numeric (float) history values. Available since 5.0.0. Enabled by default.

-
ENABLE_WEB_ACCESS_LOG

+
ENABLE_WEB_ACCESS_LOG

 
The variable sets the Access Log directive for Web server. By default, value corresponds to standard output.

-
HTTP_INDEX_FILE

+
HTTP_INDEX_FILE

 
The variable controls default index page. By default, index.php.

-
EXPOSE_WEB_SERVER_INFO

+
EXPOSE_WEB_SERVER_INFO

 
The variable allows to hide Web server and PHP versions. By default, on.

-
ZBX_MAXEXECUTIONTIME

-
The varable is PHP max_execution_time option. By default, value is 300.

-
ZBX_MEMORYLIMIT

-
The varable is PHP memory_limit option. By default, value is 128M.

-
ZBX_POSTMAXSIZE

-
The varable is PHP post_max_size option. By default, value is 16M.

-
ZBX_UPLOADMAXFILESIZE

-
The varable is PHP upload_max_filesize option. By default, value is 2M.

-
ZBX_MAXINPUTTIME

-
The varable is PHP max_input_time option. By default, value is 300.

-
ZBX_SESSION_NAME

+
ZBX_MAXEXECUTIONTIME

+
The variable is PHP max_execution_time option. By default, value is 300.

+
ZBX_MEMORYLIMIT

+
The variable is PHP memory_limit option. By default, value is 128M.

+
ZBX_POSTMAXSIZE

+
The variable is PHP post_max_size option. By default, value is 16M.

+
ZBX_UPLOADMAXFILESIZE

+
The variable is PHP upload_max_filesize option. By default, value is 2M.

+
ZBX_MAXINPUTTIME

+
The variable is PHP max_input_time option. By default, value is 300.

+
ZBX_SESSION_NAME

 
The variable is Zabbix frontend definition. String used as the name of the Zabbix frontend session cookie. By default, value is zbx_sessionid.

-
ZBX_DENY_GUI_ACCESS

+
ZBX_DENY_GUI_ACCESS

 
Enable (true) maintenance mode for Zabbix web-interface.

-
ZBX_GUI_ACCESS_IP_RANGE

+
ZBX_GUI_ACCESS_IP_RANGE

 
Array of IP addresses which are allowed for accessing to Zabbix web-interface during maintenance period.

-
ZBX_GUI_WARNING_MSG

+
ZBX_GUI_WARNING_MSG

 
Information message about maintenance period for Zabbix web-interface.

-
ZBX_DB_ENCRYPTION

+
ZBX_DB_ENCRYPTION

 
The variable allows to activate encryption for connections to Zabbix database. Even if no other environment variables are specified, connections will be TLS-encrypted if ZBX_DB_ENCRYPTION=true specified. Available since 5.0.0. Disabled by default.

-
ZBX_DB_KEY_FILE

+
ZBX_DB_KEY_FILE

 
The variable allows to specify the full path to a valid TLS key file. Available since 5.0.0.

-
ZBX_DB_CERT_FILE

+
ZBX_DB_CERT_FILE

 
The variable allows to specify the full path to a valid TLS certificate file. Available since 5.0.0.

-
ZBX_DB_CA_FILE

+
ZBX_DB_CA_FILE

 
The variable allows to specify the full path to a valid TLS certificate authority file. Available since 5.0.0.

-
ZBX_DB_VERIFY_HOST

+
ZBX_DB_VERIFY_HOST

 
The variable allows to activate host verification. Available since 5.0.0.

-
ZBX_DB_CIPHER_LIST

+
ZBX_DB_CIPHER_LIST

 
The variable allows to specify a custom list of valid ciphers. The format of the cipher list must conform to the OpenSSL standard. Available since 5.0.0.

-
ZBX_SSO_SP_KEY

+
ZBX_SSO_SP_KEY

 
The variable allows to specify a custom file path to the Service Provider (SP) private key file.

-
ZBX_SSO_SP_CERT

-
The variable allows to specify a custom file path to the Serivce Provider (SP) cert file.

-
ZBX_SSO_IDP_CERT

+
ZBX_SSO_SP_CERT

+
The variable allows to specify a custom file path to the Service Provider (SP) cert file.

+
ZBX_SSO_IDP_CERT

 
The variable allows to specify a custom file path to the SAML Certificate provided by the Identity Provider (ID) file.

-
ZBX_SSO_SETTINGS

+
ZBX_SSO_SETTINGS

 
The variable allows to specify custom SSO settings in JSON format. Available since 5.0.0.

 
Example of YAML Mapping to Sequences

-
....
+
....
   environment:
-    ZBX_SSO_SETTINGS: "{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}"
+    ZBX_SSO_SETTINGS: "{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}"
     ....
-....
+....
 

-
ZBX_ALLOW_HTTP_AUTH

+
ZBX_ALLOW_HTTP_AUTH

 
The variable allows to disable user HTTP authentication.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
-ZBX_VAULTDBPATH= # Available since 5.2.0
-ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
-VAULT_TOKEN= # Available since 5.2.0
-ZBX_VAULTPREFIX= # Available since 7.0.0
-ZBX_VAULTCERTFILE= # Available since 6.2.0
-ZBX_VAULTKEYFILE= # Available since 6.2.0
-ZBX_VAULTCACHE=false # Available since 6.2.0
+
ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
+ZBX_VAULTDBPATH= # Available since 5.2.0
+ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
+VAULT_TOKEN= # Available since 5.2.0
+ZBX_VAULTPREFIX= # Available since 7.0.0
+ZBX_VAULTCERTFILE= # Available since 6.2.0
+ZBX_VAULTKEYFILE= # Available since 6.2.0
+ZBX_VAULTCACHE=false # Available since 6.2.0
 
-ZBX_SERVER_TLS_ACTIVE=false # Available since 7.4.0
-ZBX_SERVER_TLS_CAFILE= # Available since 7.4.0
-ZBX_SERVER_TLS_CA= # Available since 7.4.0
-ZBX_SERVER_TLS_KEYFILE= # Available since 7.4.0
-ZBX_SERVER_TLS_KEY= # Available since 7.4.0
-ZBX_SERVER_TLS_CERTFILE= # Available since 7.4.0
-ZBX_SERVER_TLS_CERT= # Available since 7.4.0
-ZBX_SERVER_TLS_CERT_ISSUER= # Available since 7.4.0
-ZBX_SERVER_TLS_CERT_SUBJECT= # Available since 7.4.0
+ZBX_SERVER_TLS_ACTIVE=false # Available since 7.4.0
+ZBX_SERVER_TLS_CAFILE= # Available since 7.4.0
+ZBX_SERVER_TLS_CA= # Available since 7.4.0
+ZBX_SERVER_TLS_KEYFILE= # Available since 7.4.0
+ZBX_SERVER_TLS_KEY= # Available since 7.4.0
+ZBX_SERVER_TLS_CERTFILE= # Available since 7.4.0
+ZBX_SERVER_TLS_CERT= # Available since 7.4.0
+ZBX_SERVER_TLS_CERT_ISSUER= # Available since 7.4.0
+ZBX_SERVER_TLS_CERT_SUBJECT= # Available since 7.4.0
 
 Allowed PHP-FPM configuration options:
-PHP_FPM_PM=dynamic
-PHP_FPM_PM_MAX_CHILDREN=50
-PHP_FPM_PM_START_SERVERS=5
-PHP_FPM_PM_MIN_SPARE_SERVERS=5
-PHP_FPM_PM_MAX_SPARE_SERVERS=35
-PHP_FPM_PM_MAX_REQUESTS=0
+PHP_FPM_PM=dynamic
+PHP_FPM_PM_MAX_CHILDREN=50
+PHP_FPM_PM_START_SERVERS=5
+PHP_FPM_PM_MIN_SPARE_SERVERS=5
+PHP_FPM_PM_MAX_SPARE_SERVERS=35
+PHP_FPM_PM_MAX_REQUESTS=0
 
 Allowed Nginx configuration options:
-WEB_REAL_IP_FROM=
-WEB_REAL_IP_HEADER=
-
Allowed volumes for the Zabbix web interface container

-
/etc/ssl/nginx

-
The volume allows to enable HTTPS for the Zabbix web interface. The volume must contains three files ssl.crt, ssl.key and dhparam.pem prepared for Nginx SSL connections.

+WEB_REAL_IP_FROM=
+WEB_REAL_IP_HEADER=
+

+
Allowed volumes for the Zabbix web interface container

+
/etc/ssl/nginx

+
The volume allows to enable HTTPS for the Zabbix web interface. The volume must contain three files ssl.crt, ssl.key and dhparam.pem prepared for Nginx SSL connections.

 
Please follow official Nginx documentation to get more details about how to create certificate files.

-
/etc/zabbix/web/certs

-
The volume allows to use custom certificates for SAML authentification. The volume must contains three files sp.key, sp.crt and idp.crt. Available since 5.0.0.

-
/var/lib/zabbix/enc

+
/etc/zabbix/web/certs

+
The volume allows to use custom certificates for SAML authentication. The volume must contain three files sp.key, sp.crt and idp.crt. Available since 5.0.0.

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_SERVER_TLS_CAFILE, ZBX_SERVER_TLS_KEYFILE and ZBX_SERVER_TLS_CERTFILE variables. Additionally it is possible to use environment variables ZBX_SERVER_TLS_CA, ZBX_SERVER_TLS_KEY and ZBX_SERVER_TLS_CERT with plaintext values. Available since 7.4.0.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the web-nginx-mysql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the web-nginx-mysql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

-
Contributing

+
Known issues

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/web-nginx-pgsql/rhel/README.html b/Dockerfiles/web-nginx-pgsql/rhel/README.html
index 8fa2df12..7ac90679 100644
--- a/Dockerfiles/web-nginx-pgsql/rhel/README.html
+++ b/Dockerfiles/web-nginx-pgsql/rhel/README.html
@@ -1,12 +1,11 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix web interface?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix web interface?

 
Zabbix web interface is a part of Zabbix software. It is used to manage resources under monitoring and view monitoring statistics.

-
Zabbix web interface images

-
These are the only official Zabbix web interface Podman images. Images are updated when new releases are published.

+
Zabbix web interface images

+
Images are updated when new releases are published.

 
Zabbix web interface available in four editions:

 
    
 
  • Zabbix web-interface based on Apache2 web server with MySQL database support
    • 
@@ -15,153 +14,196 @@
 
  • Zabbix web-interface based on Nginx web server with PostgreSQL database support
    • 
 

 
The image based on Nginx web server with PostgreSQL database support.

-
How to use this image

-
Start zabbix-web-nginx-pgsql

+
How to use this image

+
Start zabbix-web-nginx-pgsql

 
Start a Zabbix web-interface container as follows:

-
podman run --name some-zabbix-web-nginx-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
-
Where some-zabbix-web-nginx-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, some-zabbix-server is IP or DNS name of Zabbix server or proxy, some-timezone is PHP like timezone name and tag is the tag specifying the version you want.

-
Linking the container to Zabbix server

-
podman run --name some-zabbix-web-nginx-pgsql --link some-zabbix-server:zabbix-server -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
-
Linking the container to PostgreSQL database

-
podman run --name some-zabbix-web-nginx-pgsql --link some-postgres-server:postgres -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER="some-user" -e POSTGRES_PASSWORD="some-password" -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
-
Container shell access and viewing Zabbix web interface logs

+
podman run \
+    --name some-zabbix-web-nginx-pgsql \
+    -e DB_SERVER_HOST="some-postgres-server" \
+    -e POSTGRES_USER="some-user" \
+    -e POSTGRES_PASSWORD="some-password" \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-pgsql-74:tag
+

+
Where some-zabbix-web-nginx-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, some-zabbix-server is IP or DNS name of Zabbix server or proxy, some-timezone is PHP like timezone name and tag is the tag specifying the version you want.

+
Linking the container to Zabbix server

+
podman run \
+    --name some-zabbix-web-nginx-pgsql \
+    --link some-zabbix-server:zabbix-server \
+    -e DB_SERVER_HOST="some-postgres-server" \
+    -e POSTGRES_USER="some-user" \
+    -e POSTGRES_PASSWORD="some-password" \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-pgsql-74:tag
+

+
Linking the container to PostgreSQL database

+
podman run \
+    --name some-zabbix-web-nginx-pgsql \
+    --link some-postgres-server:postgres \
+    -e DB_SERVER_HOST="some-postgres-server" \
+    -e POSTGRES_USER="some-user" \
+    -e POSTGRES_PASSWORD="some-password" \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-pgsql-74:tag
+

+
Container shell access and viewing Zabbix web interface logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-web-nginx-pgsql container:

-
$ podman exec -ti some-zabbix-web-nginx-pgsql /bin/bash
+
$ podman exec -ti some-zabbix-web-nginx-pgsql /bin/bash
 

-
The Zabbix web interface log is available through Podman's container log:

-
$ podman logs  some-zabbix-web-nginx-pgsql
+
The Zabbix web interface log is available through Podman's container log:

+
$ podman logs  some-zabbix-web-nginx-pgsql
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-web-nginx-pgsql image, you can adjust the configuration of the Zabbix web interface by passing one or more environment variables on the podman run command line.

-
ZBX_SERVER_HOST

+
ZBX_SERVER_HOST

 
This variable is IP or DNS name of Zabbix server. By default, value is zabbix-server.

-
ZBX_SERVER_PORT

+
ZBX_SERVER_PORT

 
This variable is port Zabbix server listening on. By default, value is 10051.

-
DB_SERVER_HOST

-
This variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'

-
DB_SERVER_PORT

-
This variable is port of PostgreSQL server. By default, value is '5432'.

-
POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_USER_FILE, POSTGRES_PASSWORD_FILE

+
DB_SERVER_HOST

+
This variable is IP or DNS name of PostgreSQL server. By default, value is 'postgres-server'

+
DB_SERVER_PORT

+
This variable is port of PostgreSQL server. By default, value is '5432'.

+
POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_USER_FILE, POSTGRES_PASSWORD_FILE

 
These variables are used by Zabbix web interface to connect to Zabbix database. With the _FILE 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 POSTGRES_USER or POSTGRES_USER_FILE!

-
podman run --name some-zabbix-web-nginx-pgsql -e DB_SERVER_HOST="some-postgres-server" -v ./.POSTGRES_USER:/run/secrets/POSTGRES_USER -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -v ./.POSTGRES_PASSWORD:/run/secrets/POSTGRES_PASSWORD -e POSTGRES_PASSWORD_FILE=/var/run/secrets/POSTGRES_PASSWORD -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
+
podman run \
+    --name some-zabbix-web-nginx-pgsql \
+    -e DB_SERVER_HOST="some-postgres-server" \
+    -v ./.POSTGRES_USER:/run/secrets/POSTGRES_USER \
+    -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER \
+    -v ./.POSTGRES_PASSWORD:/run/secrets/POSTGRES_PASSWORD \
+    -e POSTGRES_PASSWORD_FILE=/var/run/secrets/POSTGRES_PASSWORD \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-pgsql-74:tag
 

 
With Docker Swarm or Kubernetes this works with secrets. That way it is replicated in your cluster!

-
printf "zabbix" | podman secret create POSTGRES_USER -
-printf "zabbix" | podman secret create POSTGRES_PASSWORD -
-podman run --name some-zabbix-web-nginx-pgsql -e DB_SERVER_HOST="some-postgres-server" -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER -e POSTGRES_PASSWORD_FILE=/run/secrets/POSTGRES_PASSWORD -e ZBX_SERVER_HOST="some-zabbix-server" -e PHP_TZ="some-timezone" -d zabbix/zabbix-web-nginx-pgsql:tag
+
printf "zabbix" | podman secret create POSTGRES_USER -
+printf "zabbix" | podman secret create POSTGRES_PASSWORD -
+podman run \
+    --name some-zabbix-web-nginx-pgsql \
+    -e DB_SERVER_HOST="some-postgres-server" \
+    -e POSTGRES_USER_FILE=/run/secrets/POSTGRES_USER \
+    -e POSTGRES_PASSWORD_FILE=/run/secrets/POSTGRES_PASSWORD \
+    -e ZBX_SERVER_HOST="some-zabbix-server" \
+    -e PHP_TZ="some-timezone" \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-pgsql-74:tag
 

 
By default, values for POSTGRES_USER and POSTGRES_PASSWORD are zabbix, zabbix.

-
POSTGRES_DB

+
POSTGRES_DB

 
The variable is Zabbix database name. By default, value is zabbix.

-
POSTGRES_USE_IMPLICIT_SEARCH_PATH

-
In some setups, for example including PgBouncer, setting the search_path via connection parameters fails. If this variable is set to "true", the image skips setting the search_path and trusts that the search_path of the Zabbix user is setup correctly in PostgreSQL database.

-
ZBX_HISTORYSTORAGEURL

+
POSTGRES_USE_IMPLICIT_SEARCH_PATH

+
In some setups, for example including PgBouncer, setting the search_path via connection parameters fails. If this variable is set to "true", the image skips setting the search_path and trusts that the search_path of the Zabbix user is setup correctly in PostgreSQL database.

+
ZBX_HISTORYSTORAGEURL

 
History storage HTTP[S] URL. This parameter is used for Elasticsearch setup. Available since 3.4.5.

-
ZBX_HISTORYSTORAGETYPES

-
Array of value types to be sent to the history storage. An example: ['uint', 'dbl']. This parameter is used for Elasticsearch setup. Available since 3.4.5.

-
PHP_TZ

-
The variable is timezone in PHP format. Full list of supported timezones are available on php.net. By default, value is 'Europe/Riga' and system timezone since Zabbix 5.2.0.

-
ZBX_SERVER_NAME

+
ZBX_HISTORYSTORAGETYPES

+
Array of value types to be sent to the history storage. An example: ['uint', 'dbl']. This parameter is used for Elasticsearch setup. Available since 3.4.5.

+
PHP_TZ

+
The variable is timezone in PHP format. Full list of supported timezones are available on php.net. By default, value is 'Europe/Riga' and system timezone since Zabbix 5.2.0.

+
ZBX_SERVER_NAME

 
The variable is visible Zabbix installation name in right or left top corner of the web interface.

-
DB_DOUBLE_IEEE754

+
DB_DOUBLE_IEEE754

 
Use IEEE754 compatible value range for 64-bit Numeric (float) history values. Available since 5.0.0. Enabled by default.

-
ENABLE_WEB_ACCESS_LOG

+
ENABLE_WEB_ACCESS_LOG

 
The variable sets the Access Log directive for Web server. By default, value corresponds to standard output.

-
HTTP_INDEX_FILE

+
HTTP_INDEX_FILE

 
The variable controls default index page. By default, index.php.

-
EXPOSE_WEB_SERVER_INFO

+
EXPOSE_WEB_SERVER_INFO

 
The variable allows to hide Web server and PHP versions. By default, on.

-
ZBX_MAXEXECUTIONTIME

-
The varable is PHP max_execution_time option. By default, value is 300.

-
ZBX_MEMORYLIMIT

-
The varable is PHP memory_limit option. By default, value is 128M.

-
ZBX_POSTMAXSIZE

-
The varable is PHP post_max_size option. By default, value is 16M.

-
ZBX_UPLOADMAXFILESIZE

-
The varable is PHP upload_max_filesize option. By default, value is 2M.

-
ZBX_MAXINPUTTIME

-
The varable is PHP max_input_time option. By default, value is 300.

-
ZBX_SESSION_NAME

+
ZBX_MAXEXECUTIONTIME

+
The variable is PHP max_execution_time option. By default, value is 300.

+
ZBX_MEMORYLIMIT

+
The variable is PHP memory_limit option. By default, value is 128M.

+
ZBX_POSTMAXSIZE

+
The variable is PHP post_max_size option. By default, value is 16M.

+
ZBX_UPLOADMAXFILESIZE

+
The variable is PHP upload_max_filesize option. By default, value is 2M.

+
ZBX_MAXINPUTTIME

+
The variable is PHP max_input_time option. By default, value is 300.

+
ZBX_SESSION_NAME

 
The variable is Zabbix frontend definition. String used as the name of the Zabbix frontend session cookie. By default, value is zbx_sessionid.

-
ZBX_DENY_GUI_ACCESS

+
ZBX_DENY_GUI_ACCESS

 
Enable (true) maintenance mode for Zabbix web-interface.

-
ZBX_GUI_ACCESS_IP_RANGE

+
ZBX_GUI_ACCESS_IP_RANGE

 
Array of IP addresses which are allowed for accessing to Zabbix web-interface during maintenance period.

-
ZBX_GUI_WARNING_MSG

+
ZBX_GUI_WARNING_MSG

 
Information message about maintenance period for Zabbix web-interface.

-
ZBX_DB_ENCRYPTION

+
ZBX_DB_ENCRYPTION

 
The variable allows to activate encryption for connections to Zabbix database. Even if no other environment variables are specified, connections will be TLS-encrypted if ZBX_DB_ENCRYPTION=true specified. Available since 5.0.0. Disabled by default.

-
ZBX_DB_KEY_FILE

+
ZBX_DB_KEY_FILE

 
The variable allows to specify the full path to a valid TLS key file. Available since 5.0.0.

-
ZBX_DB_CERT_FILE

+
ZBX_DB_CERT_FILE

 
The variable allows to specify the full path to a valid TLS certificate file. Available since 5.0.0.

-
ZBX_DB_CA_FILE

+
ZBX_DB_CA_FILE

 
The variable allows to specify the full path to a valid TLS certificate authority file. Available since 5.0.0.

-
ZBX_DB_VERIFY_HOST

+
ZBX_DB_VERIFY_HOST

 
The variable allows to activate host verification. Available since 5.0.0.

-
ZBX_SSO_SP_KEY

+
ZBX_SSO_SP_KEY

 
The variable allows to specify a custom file path to the Service Provider (SP) private key file.

-
ZBX_SSO_SP_CERT

-
The variable allows to specify a custom file path to the Serivce Provider (SP) cert file.

-
ZBX_SSO_IDP_CERT

+
ZBX_SSO_SP_CERT

+
The variable allows to specify a custom file path to the Service Provider (SP) cert file.

+
ZBX_SSO_IDP_CERT

 
The variable allows to specify a custom file path to the SAML Certificate provided by the Identity Provider (ID) file.

-
ZBX_SSO_SETTINGS

+
ZBX_SSO_SETTINGS

 
The variable allows to specify custom SSO settings in JSON format. Available since 5.0.0.

 
Example of YAML Mapping to Sequences

-
....
+
....
   environment:
-    ZBX_SSO_SETTINGS: "{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}"
+    ZBX_SSO_SETTINGS: "{'baseurl': 'https://zabbix-docker.mydomain.com', 'use_proxy_headers': true, 'strict': false}"
     ....
-....
+....
 

-
ZBX_ALLOW_HTTP_AUTH

+
ZBX_ALLOW_HTTP_AUTH

 
The variable allows to disable user HTTP authentication.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
-ZBX_VAULTDBPATH= # Available since 5.2.0
-ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
-VAULT_TOKEN= # Available since 5.2.0
-ZBX_VAULTPREFIX= # Available since 7.0.0
-ZBX_VAULTCERTFILE= # Available since 6.2.0
-ZBX_VAULTKEYFILE= # Available since 6.2.0
-ZBX_VAULTCACHE=false # Available since 6.2.0
+
ZBX_VAULT=HashiCorp # Allowed values: HashiCorp, CyberArk. Required when Vault is used. Available since 6.2.0
+ZBX_VAULTDBPATH= # Available since 5.2.0
+ZBX_VAULTURL=https://127.0.0.1:8200 # Available since 5.2.0
+VAULT_TOKEN= # Available since 5.2.0
+ZBX_VAULTPREFIX= # Available since 7.0.0
+ZBX_VAULTCERTFILE= # Available since 6.2.0
+ZBX_VAULTKEYFILE= # Available since 6.2.0
+ZBX_VAULTCACHE=false # Available since 6.2.0
 
-ZBX_SERVER_TLS_ACTIVE=false # Available since 7.4.0
-ZBX_SERVER_TLS_CAFILE= # Available since 7.4.0
-ZBX_SERVER_TLS_CA= # Available since 7.4.0
-ZBX_SERVER_TLS_KEYFILE= # Available since 7.4.0
-ZBX_SERVER_TLS_KEY= # Available since 7.4.0
-ZBX_SERVER_TLS_CERTFILE= # Available since 7.4.0
-ZBX_SERVER_TLS_CERT= # Available since 7.4.0
-ZBX_SERVER_TLS_CERT_ISSUER= # Available since 7.4.0
-ZBX_SERVER_TLS_CERT_SUBJECT= # Available since 7.4.0
+ZBX_SERVER_TLS_ACTIVE=false # Available since 7.4.0
+ZBX_SERVER_TLS_CAFILE= # Available since 7.4.0
+ZBX_SERVER_TLS_CA= # Available since 7.4.0
+ZBX_SERVER_TLS_KEYFILE= # Available since 7.4.0
+ZBX_SERVER_TLS_KEY= # Available since 7.4.0
+ZBX_SERVER_TLS_CERTFILE= # Available since 7.4.0
+ZBX_SERVER_TLS_CERT= # Available since 7.4.0
+ZBX_SERVER_TLS_CERT_ISSUER= # Available since 7.4.0
+ZBX_SERVER_TLS_CERT_SUBJECT= # Available since 7.4.0
 
 Allowed PHP-FPM configuration options:
-PHP_FPM_PM=dynamic
-PHP_FPM_PM_MAX_CHILDREN=50
-PHP_FPM_PM_START_SERVERS=5
-PHP_FPM_PM_MIN_SPARE_SERVERS=5
-PHP_FPM_PM_MAX_SPARE_SERVERS=35
-PHP_FPM_PM_MAX_REQUESTS=0
+PHP_FPM_PM=dynamic
+PHP_FPM_PM_MAX_CHILDREN=50
+PHP_FPM_PM_START_SERVERS=5
+PHP_FPM_PM_MIN_SPARE_SERVERS=5
+PHP_FPM_PM_MAX_SPARE_SERVERS=35
+PHP_FPM_PM_MAX_REQUESTS=0
 
 Allowed Nginx configuration options:
-WEB_REAL_IP_FROM=
-WEB_REAL_IP_HEADER=
-
Allowed volumes for the Zabbix web interface container

-
/etc/ssl/nginx

-
The volume allows to enable HTTPS for the Zabbix web interface. The volume must contains three files ssl.crt, ssl.key and dhparam.pem prepared for Nginx SSL connections.

+WEB_REAL_IP_FROM=
+WEB_REAL_IP_HEADER=
+

+
Allowed volumes for the Zabbix web interface container

+
/etc/ssl/nginx

+
The volume allows to enable HTTPS for the Zabbix web interface. The volume must contain three files ssl.crt, ssl.key and dhparam.pem prepared for Nginx SSL connections.

 
Please follow official Nginx documentation to get more details about how to create certificate files.

-
/etc/zabbix/web/certs

-
The volume allows to use custom certificates for SAML authentification. The volume must contains three files sp.key, sp.crt and idp.crt. Available since 5.0.0.

-
/var/lib/zabbix/enc

+
/etc/zabbix/web/certs

+
The volume allows to use custom certificates for SAML authentication. The volume must contain three files sp.key, sp.crt and idp.crt. Available since 5.0.0.

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_SERVER_TLS_CAFILE, ZBX_SERVER_TLS_KEYFILE and ZBX_SERVER_TLS_CERTFILE variables. Additionally it is possible to use environment variables ZBX_SERVER_TLS_CA, ZBX_SERVER_TLS_KEY and ZBX_SERVER_TLS_CERT with plaintext values. Available since 7.4.0.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the web-nginx-pgsql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the web-nginx-pgsql/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

-
Contributing

+
Known issues

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.

diff --git a/Dockerfiles/web-service/rhel/README.html b/Dockerfiles/web-service/rhel/README.html
index 362817a0..35777b8b 100644
--- a/Dockerfiles/web-service/rhel/README.html
+++ b/Dockerfiles/web-service/rhel/README.html
@@ -1,35 +1,44 @@
-
logo

-
What is Zabbix?

+
What is Zabbix?

 
Zabbix is an enterprise-class open source distributed monitoring solution.

 
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.

-
For more information and related downloads for Zabbix components, please visit https://hub.docker.com/u/zabbix/ and https://zabbix.com

-
What is Zabbix web service?

+
For more information and related downloads for Zabbix components, please visit Docker Hub and zabbix.com

+
What is Zabbix web service?

 
Zabbix web service for performing various tasks using headless web browser (for example, reporting).

-
Zabbix web service images

-
These are the only official Zabbix web service Podman images. Images are updated when new releases are published.

-
How to use this image

-
Start zabbix-web-service

+
Zabbix web service images

+
Images are updated when new releases are published.

+
How to use this image

+
Start zabbix-web-service

 
Start a Zabbix web service container as follows:

-
podman run --name some-zabbix-web-service -e ZBX_ALLOWEDIP="some-zabbix-server" --cap-add=SYS_ADMIN -d zabbix/zabbix-web-service:tag
-
Where some-zabbix-web-service is the name you want to assign to your container, some-zabbix-server is IP or DNS name of Zabbix server and tag is the tag specifying the version you want.

-
Connects from Zabbix server in other containers

+
podman run \
+    --name some-zabbix-web-service \
+    -e ZBX_ALLOWEDIP="some-zabbix-server" \
+    --cap-add=SYS_ADMIN \
+    -d registry.connect.redhat.com/zabbix/zabbix-web-service-74:tag
+

+
Where some-zabbix-web-service is the name you want to assign to your container, some-zabbix-server is IP or DNS name of Zabbix server and tag is the tag specifying the version you want.

+
Connects from Zabbix server in other containers

 
This image exposes the standard Zabbix web service port (10053) to perform communication, so container linking makes Zabbix web service instance available to Zabbix server containers. Start your application container like this in order to link it to the Zabbix web service container:

-
$ podman run --name some-zabbix-server --link some-zabbix-web-service:zabbix-web-service -e ZBX_STARTREPORTWRITERS="2" -e ZBX_WEBSERVICEURL="http://some-zabbix-web-service:10053/report" -d zabbix/zabbix-server:latest
+
$ podman run \
+    --name some-zabbix-server \
+    --link some-zabbix-web-service:zabbix-web-service \
+    -e ZBX_STARTREPORTWRITERS="2" \
+    -e ZBX_WEBSERVICEURL="http://some-zabbix-web-service:10053/report" \
+    -d zabbix/zabbix-server:latest
 

-
Container shell access and viewing Zabbix web service logs

+
Container shell access and viewing Zabbix web service logs

 
The podman exec command allows you to run commands inside a Podman container. The following command line will give you a bash shell inside your zabbix-web-service container:

-
$ podman exec -ti some-zabbix-web-service /bin/bash
+
$ podman exec -ti some-zabbix-web-service /bin/bash
 

-
The Zabbix web service log is available through Podman's container log:

-
$ podman logs some-zabbix-web-service
+
The Zabbix web service log is available through Podman's container log:

+
$ podman logs some-zabbix-web-service
 

-
Environment Variables

+
Environment Variables

 
When you start the zabbix-web-service image, you can adjust the configuration of the Zabbix web service by passing one or more environment variables on the podman run command line.

-
ZBX_ALLOWEDIP

+
ZBX_ALLOWEDIP

 
This variable is IP or DNS name or list of IP / DNS names of Zabbix server. By default, value is zabbix-server.

-
ZBX_LISTENPORT

+
ZBX_LISTENPORT

 
Listen port for incoming request. By default, value is 10053.

-
ZBX_DEBUGLEVEL

+
ZBX_DEBUGLEVEL

 
The variable is used to specify debug level. By default, value is 3. It is DebugLevel parameter in zabbix_web_service.conf. Allowed values are listed below:

 
    
 
  • 0 - basic information about starting and stopping of Zabbix processes;
    • 
@@ -39,32 +48,34 @@
 
  • 4 - for debugging (produces lots of information)
    • 
 
  • 5 - extended debugging (produces even more information)
    • 
 

-
ZBX_TIMEOUT

+
ZBX_TIMEOUT

 
The variable is used to specify timeout for processing requests. By default, value is 3.

-
Other variables

+
Other variables

 
Additionally the image allows to specify many other environment variables listed below:

-
ZBX_TLSACCEPT=unencrypted
-ZBX_TLSCAFILE=
-ZBX_TLSCA=
-ZBX_TLSCERTFILE=
-ZBX_TLSCERT=
-ZBX_TLSKEYFILE=
-ZBX_TLSKEY=
-ZBX_IGNOREURLCERTERRORS=0
-
Default values of these variables are specified after equal sign.

+
ZBX_TLSACCEPT=unencrypted
+ZBX_TLSCAFILE=
+ZBX_TLSCA=
+ZBX_TLSCERTFILE=
+ZBX_TLSCERT=
+ZBX_TLSKEYFILE=
+ZBX_TLSKEY=
+ZBX_IGNOREURLCERTERRORS=0
+

+
Default values of these variables are specified after equal sign.

 
Please use official documentation for zabbix_web_service.conf to get more information about the variables.

-
Allowed volumes for the Zabbix web service container

-
/var/lib/zabbix/enc

+
Allowed volumes for the Zabbix web service container

+
/var/lib/zabbix/enc

 
The volume is used to store TLS related files. These file names are specified using ZBX_TLSCAFILE, ZBX_TLSCERTFILE and ZBX_TLSKEYFILE variables. Additionally it is possible to use environment variables ZBX_TLSCA, ZBX_TLSCERT and ZBX_TLSKEY with plaintext values.

-
User Feedback

-
Documentation

-
Documentation for this image is stored in the web-service/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

-
Issues

+
User Feedback

+
Documentation

+
Documentation for this image is stored in the web-service/ directory of the zabbix/zabbix-docker GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

+
Issues

 
If you have any problems with or questions about this image, please contact us through a GitHub issue.

-
Known issues

+
Known issues

 
Zabbix web services uses Google Chromium with headless mode. Because of restrictions you may see the following error during report generation:

-
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
-
To avoid the issue it is required to add SYS_ADMIN capability for Zabbix web service. The capability is redundant and allow too much.

-
Contributing

+
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
+

+
To avoid the issue it is required to add SYS_ADMIN capability for Zabbix web service. The capability is redundant and allow too much.

+
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.

 
Before you start to code, we recommend discussing your plans through a GitHub issue, 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.