Following up on the topic of enabling Redis TLS option recommendation to file a bug report:
docker compose services
` redis:
image: redis:alpine3.15
container_name: redis
hostname: redis04
volumes:
The Redis configuration is
bind 0.0.0.0 protected-mode no port 0 loglevel notice tls-port 6379 tls-cert-file /usr/local/etc/redis/ssl/redis.pem tls-key-file /usr/local/etc/redis/ssl/redis-key.pem tls-ca-cert-file /usr/local/etc/redis/ssl/allcacerts.pem proc-title-template "{title} {listen-addr} {server-mode}"
The Redis service has been confirmed to function as intended. When the icingadb service is started, the following errors are reported:
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 | icingadb | goroutine 1 [running]: icingadb | [github.com/icinga/icingadb/pkg/utils.Fatal(...)](http://github.com/icinga/icingadb/pkg/utils.Fatal(...)) icingadb | /github/workspace/pkg/utils/utils.go:118 icingadb | [github.com/icinga/icingadb/internal/command.New()](http://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
It was also suggested that the form of the environment variable changed due to this possible issue, which then begs the question of what form does the ENVIRONMENT variable take on? Does it need to be '- ICINGADB_REDIS_TLS_TLS=true'
Following up on the topic of enabling Redis TLS option recommendation to file a bug report: docker compose services ` redis: image: redis:alpine3.15 container_name: redis hostname: redis04 volumes:
icingadb: image: icinga/icingadb:master container_name: icingadb hostname: icingadb04 environment:
- ICINGADB_DATABASE_HOST=velolabdock04
- ICINGADB_DATABASE_TYPE=pgsql
- ICINGADB_DATABASE_PORT=5432
The Redis configuration is
bind 0.0.0.0 protected-mode no port 0 loglevel notice tls-port 6379 tls-cert-file /usr/local/etc/redis/ssl/redis.pem tls-key-file /usr/local/etc/redis/ssl/redis-key.pem tls-ca-cert-file /usr/local/etc/redis/ssl/allcacerts.pem proc-title-template "{title} {listen-addr} {server-mode}"The Redis service has been confirmed to function as intended. When the icingadb service is started, the following errors are reported:
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 | icingadb | goroutine 1 [running]: icingadb | [github.com/icinga/icingadb/pkg/utils.Fatal(...)](http://github.com/icinga/icingadb/pkg/utils.Fatal(...)) icingadb | /github/workspace/pkg/utils/utils.go:118 icingadb | [github.com/icinga/icingadb/internal/command.New()](http://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 2It was also suggested that the form of the environment variable changed due to this possible issue, which then begs the question of what form does the ENVIRONMENT variable take on? Does it need to be '- ICINGADB_REDIS_TLS_TLS=true'