After changing the image to icinga/icingadb:master, and using ‘- ICINGADB_REDIS_TLS=true’ in the environment the result did not change:
[+] Running 3/3
⠿ Container redis Running 0.0s
⠿ Container mysql Running 0.0s
⠿ Container icingadb Recreated 1.7s
Attaching to icingadb
icingadb | 2022-04-27T20:12:58.991Z DEBUG entrypoint/main.go:40 translating env vars to YAML config
icingadb | 2022-04-27T20:12:58.993Z DEBUG entrypoint/main.go:85 checking SQL database
icingadb | 2022-04-27T20:12:59.005Z 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 |
icingadb | goroutine 1 [running]:
icingadb | github.com/icinga/icingadb/pkg/utils.Fatal(...)
icingadb | /github/workspace/pkg/utils/utils.go:114
icingadb | github.com/icinga/icingadb/internal/command.New()
icingadb | /github/workspace/internal/command/command.go:41 +0x185
icingadb | main.run()
icingadb | /github/workspace/cmd/icingadb/main.go:40 +0x57
icingadb | main.main()
icingadb | /github/workspace/cmd/icingadb/main.go:36 +0x19
icingadb exited with code 2
Regarding the possible bug Unfortunately I do not understand what the ENV form should be for enabling REDIS TLS.