syrcx created an issue (kamailio/kamailio#4401)
**Description**
I’m trying to connect Kamailio to a Redis instance that requires TLS.
My configuration looks like this:
```
loadmodule "ndb_redis.so"
modparam("ndb_redis", "server",
"name=con1;addr=$env(REDIS_ADDR);port=$env(REDIS_PORT);pass=$env(REDIS_PASSWORD);tls=1")
```
However, when using the official Kamailio Docker image with the kamailio-redis
package installed, the connection fails because TLS support is not available.
Environment / Dockerfile
```
FROM ghcr.io/kamailio/kamailio-ci:5.8.4-alpine
RUN apk update \
&& apk add --no-cache kamailio-redis ca-certificates redis \
&& update-ca-certificates
```
**Issue Details**
After adding kamailio-redis, I expected TLS support to be available. Instead, I
found that libhiredis_ssl.so is missing from the image.
Checking dependencies of ndb_redis.so shows that only the non-SSL libhiredis
library is linked:
```
$ readelf -d /usr/lib/kamailio/modules/ndb_redis.so | grep NEEDED
0x0000000000000001 (NEEDED) Shared library: [libhiredis.so.1.1.0]
0x0000000000000001 (NEEDED) Shared library: [libc.musl-x86_64.so.1]
```
>From what I’ve found, enabling TLS requires building Kamailio (and/or hiredis)
>with SSL support using -DWITH_SSL.
**Question**
What is the recommended way to enable Redis TLS support in Kamailio when using
the official Docker image?
Should I rebuild Kamailio from source with -DWITH_SSL?
Or is there a lighter-weight approach (e.g., an Alpine package that already
provides libhiredis_ssl.so) that I may be missing?
Appreciate clarification on the best practice for enabling Redis TLS in
Docker-based deployments.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4401
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/[email protected]>_______________________________________________
Kamailio - Development Mailing List -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
