TubeArchivist
TubeArchivist runs on the Synology NAS via Docker Compose, self-hosting a searchable archive of downloaded YouTube content (Elasticsearch + Redis + the TubeArchivist app itself).
Why this needed real troubleshooting
Running Elasticsearch on Synology's DSM kernel isn't fully straightforward: newer Elasticsearch releases require a Linux kernel feature (SECCOMP) that Synology's kernel doesn't compile in. The fix is version-pinning Elasticsearch to the last release that still works without it, rather than fighting the kernel.
Other Synology-specific quirks
- Synology's Container Manager doesn't always auto-join containers to the same Docker network even when they're defined in one Compose file — an explicit named network avoids silent connectivity failures between the app, Elasticsearch, and Redis.
- A version upgrade of the app itself required a very specific step-by-step path (skipping versions breaks the database migration) rather than jumping straight to the latest release.
What's backed up
| Data | Included in NAS backup? |
|---|---|
| Downloaded media files | Yes, via the NAS's own backup volumes |
| Elasticsearch metadata/index | Yes, via the NAS's own backup volumes |
| Redis cache | No — safe to delete/rebuild, only holds session data |