Database details in docker-server

[quackduck]

When I install or upgrade zabbix server, do I need to do anything with the database? The database is in a container.

https://www.zabbix.com/documentation/current/en/manual/installation/containers

At the top of the article, there's an "Attention" box. What is it really saying or demanding from me?

Do I need to care about this when I upgrade the zabbix image?

[cyber]

At the top of the article, there's an "Attention" box. What is it really saying or demanding from me?

If you upgrade, you need to have mentioned config parameter set in DB. You can do it manually from console and then run your new server first time (which will do upgrade tasks in DB also), after that you can restart your db container and that temporarily set config option will be disabled again. OR .. you can enable that option through DB config file, which I would assume is not overwritten with container restart and option will be kept until you decide to disable it..

[quackduck]

Thank you for explaining that and how to use it.

[quackduck]

Is it just me that can't read, or is the manual broken?
There's a lot of broken english in all Zabbix texts in general.

[guntis_liepins]

If you install zabbix with containers you need to have to install databases - either in containers or separate servers and run database scripts.

I would recommend using composed installation from same page.
composed installation will start database as well and will create zabbix database structure by running init containers
You just need to set DB password in these files.
./env_vars/.POSTGRES_USER
./env_vars/.POSTGRES_PASSWORD
I however prefer not touch any file in repo and specify them in startup script, created outside cloned repo
Just example

#!/bin/bash
export ZABBIX_WEB_NGINX_HTTP_PORT=8080
export ZABBIX_WEB_NGINX_HTTPS_PORT=8443
export POSTGRES_USER=johndoe
export POSTGRES_PASSWORD=pasword
export ZABBIX_ALPINE_IMAGE_TAG="alpine-7.0.21"
docker compose -f ./zabbix-docker/docker-compose_v3_alpine_pgsql_latest.yaml up -d --force-recreate

[cyber]

At the top of the article, there's an "Attention" box. What is it really saying or demanding from me?

If you upgrade, you need to have mentioned config parameter set in DB. You can do it manually from console and then run your new server first time (which will do upgrade tasks in DB also), after that you can restart your db container and that temporarily set config option will be disabled again. OR .. you can enable that option through DB config file, which I would assume is not overwritten with container restart and option will be kept until you decide to disable it..

[quackduck]

Thank you for explaining that and how to use it.