In putting together an Icinga2 and IcingaWeb2 containerized setup, it was discovered that IcingaDB was a frequently mentioned requirement, but was not provided with either docker container images.
Icinga DB version docker icinga/icingadb:1.0.0-rc2
Configuration of docker-compose.yml
Error during container start:
icingadb | 2022-04-17T07:25:07.517Z DEBUG entrypoint/main.go:40 translating env vars to YAML config
icingadb | 2022-04-17T07:25:07.518Z DEBUG entrypoint/main.go:85 checking SQL database
icingadb | 2022-04-17T07:25:07.528Z DEBUG entrypoint/main.go:79 starting actual daemon via exec(3)
icingadb | panic: can’t parse YAML file /etc/icingadb/config.ini: cannot unmarshal string into Go struct field Config.Redis of type bool
icingadb | goroutine 1 [running]:
icingadb | github.com/icinga/icingadb/pkg/utils.Fatal(...)
icingadb | /github/workspace/pkg/utils/utils.go:118
icingadb | github.com/icinga/icingadb/internal/command.New()
icingadb | /github/workspace/internal/command/command.go:41 +0x173
icingadb | main.run()
icingadb | /github/workspace/cmd/icingadb/main.go:38 +0x57
icingadb | main.main()
icingadb | /github/workspace/cmd/icingadb/main.go:34 +0x19
icingadb exited with code 2
The IcingaDB docker page states that each of the configuration options for IcingaDB has and environment that corresponds to it.
The question is what is the value of ‘ICINGADB_REDIS_TLS=enable’ supposed to be, or if the environment form is even correct? The configuration documentation is not very forthcoming. It simply states ‘Option TLS, Optional, Whether to use TLS’. The IcingaDB configuration file example does not address have the TLS example either, unfortunately. The following values have been tried with no difference in behaviour:
There are other questions about how the Postgre DB option is supposed to work with the IcingaDB container configuration, but that is for another post.