utilizes
Issues running vanilla configuration on DSM 7
When I was looking for official docs on the matter I found two links which give you slightly different instructions:
They differ in some aspects, but ultimately, as I tried to run and fix the provided docker-compose.yml for DSM 7, I started encountering some issues 👇.
MongoDB 5 requires AVX Support on the NAS CPU
WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!
So what exactly is AVX? 🤔
Advanced Vector Extensions (AVX) are extensions to the x86 instruction set architecture for microprocessors from Intel and Advanced Micro Devices (AMD). They were proposed by Intel in March 2008 and first supported by Intel with the Sandy Bridge[1] processor shipping in Q1 2011 and later by AMD with the Bulldozer[2] processor shipping in Q3 2011. AVX provides new features, new instructions and a new coding scheme. - this is not a thing in Celeron CPUs and as such support on Synology NAS will be reduced, especially for the home and semi-pro variants of their products.
✅ Solution: Downgrade MongoDB to latest 4.x which doesn't require AVX support.
Graylog 5 requires MongoDB 5
org.graylog2.bootstrap.preflight.PreflightCheckException: You're running MongoDB 4.4.18 but Graylog requires at least MongoDB 5.0.0. Please upgrade.
As an end-user who primarily wants to ingest logs into Graylog and be able to query them, I was not overly concerned with this downgrade.
✅ Solution: Downgrade Graylog to latest 4.x which doesn't require MongoDB 5.x
Incorrect mapping of elasticsearch folder
This is the issue that really got me. When playing with
dockerevery time I have path access issues it's either the user I'm defining lacking permissions of the local folder I'm mapping simply doesn't exist. While troubleshooting this, I went nuts trying to find why docker didn't have access to the folder in question, to the point I gave up. After a day or so I picked up this project again, and then I found a Stackoverflow post suggesting to change the path on the docker image itself:

posted on