The discussion revolves around installing Discourse on a Synology NAS using Docker. dvdstelt faces issues with the installation, specifically not finding the discourse-setup file and familiar folders. Mittineague mentions that Discourse setup checks for device mapper instead of AUFS. elijah suggests that the official install might not be suitable for this environment and proposes alternatives, such as building images on another system or running containers inside containers.
dvdstelt eventually gives up on the installation and instead uses Communiteq for hosting, but still expresses interest in having a test environment on the NAS. Malek1 also encounters the same difficulties and inquires about a solution.
I am running DSM 6.1.3 on my Synology NAS, including Docker. I’d love to get Discourse running on it as a test environment. For some reason I can’t seem to get it working.
Running Docker I can get the docker image. But when I SSH into it (via Docker Terminal on my Synology web interface) I can browse the various folders. But nowhere do I see files and folders I’m used to. Like the discourse-setup file and everything.
Anyone any idea how to progress from here? It seems ridiculous to install Ubuntu inside Docker and then install Docker inside that Ubuntu image. Kind of like Inception.
Having not used this product, I think the official install is a bad fit for this environment.
This appears to be for running simple independent containers, which works well if you have all your data on a file share or separate database. In the case of the standard Discourse install, the container is the app, the database files live on the local disk, and the container management is a script called launcher.
For Synology, it seems you’d want a way to build images on another system, arrange for the the /share/ mount to be on a file server somewhere, and replace launcher with the Synology controls. Doable, but not a simple drop in.