-
|
Just updated my AIO containers using the latest branch (Nextcloud 30) and had Imaginary and Fulltextsearch addons enabled through the AIO interface. This setup worked without issues until yesterday and now the fulltextsearch container does not start up due to missing seccomp feature of the Synology DSM kernel. Is there some way to disable this (Somehow it should be possible to disable this on elasticsearch's end but i could not find a way for the containter to recognize this)? The log shows: And disabling this should be possible with one of the 2 env vars (bootstrap.system_call_filter) like here |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 10 replies
-
|
I have the same problem, did you find a solution? |
Beta Was this translation helpful? Give feedback.
-
|
Have the same issue. I just removed the container for now. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, so if we set |
Beta Was this translation helpful? Give feedback.
-
|
See #5775 and https://www.elastic.co/guide/en/elasticsearch/reference/8.17/bootstrap-checks-syscall-filter.html |
Beta Was this translation helpful? Give feedback.
-
|
To check if your kernel support If you see this |
Beta Was this translation helpful? Give feedback.
-
|
For Unraid, I found this to be a good check: You should see something like: Follow that up with something like this: You should see something like this: If your output looks like that, it means seccomp is enabled and enforced inside containers. So you're good to go. |
Beta Was this translation helpful? Give feedback.
-
|
Solution:
HAPPY indexing! |
Beta Was this translation helpful? Give feedback.

See #5775 and https://www.elastic.co/guide/en/elasticsearch/reference/8.17/bootstrap-checks-syscall-filter.html