- Used Zammad version:
Package zammad · GitHub
bitnami/elasticsearch:7.17.26
Package zammad · GitHub
memcached:1.6.34-alpine
Package zammad · GitHub
postgres:17.2-alpine
Package zammad · GitHub
redis:7.4.2-alpine
Package zammad · GitHub
Package zammad · GitHub - Used Zammad installation type: (source, package, docker-compose, …)
docker-compose / Portainer via GitHub - Operating system:
Synology NAS - Browser + version:
All Browsers
Expected behavior:
Hi,
I installed Zammad using Docker Compose and the GitHub repository (with no custom settings). While the installation process worked fine overall, I encountered an issue with Elasticsearch.
After some research, I discovered that my Synology NAS is unable to run Elasticsearch 8 (EL8) due to a kernel error. I found a potential workaround involving the use of a environment variable in Portainer to disable the kernel settings. However, this deactivation is only supported with Elasticsearch versions earlier than 8.
To address this, I downgraded Elasticsearch to version 7.17.26. While most functionality is now operational, the INIT container stops at the following point:
I, [2025-01-17T11:45:27.944313#61-6320] INFO -- : Setting.set('es_index', "zammad")
The container exits with code 0.
I’m wondering if this issue could stem from compatibility problems between the Elasticsearch 7 container and the latest Zammad version. Specifically:
- Is the Elasticsearch 7 container incompatible with the latest Zammad release?
- If so, would it be possible to downgrade the entire Zammad setup (including Elasticsearch) to an earlier version that is compatible with Elasticsearch 7?
- Alternatively, is there a way to resolve this issue while using the latest Zammad version alongside Elasticsearch 7?
Thank you for your support!
Best regards