Synology Install Error about jump

[daledavies]

See if you can check in the container if you really do have a sites.json file mounted there, if so what are the permissions etc.

I don't know what difference the Synology NAS makes but docker-compose should create the mapped directories locally if they don't exist, so something has gone wrong there if you had to create them yourself.

[daledavies]

It really sounds like the directories have the wrong permissions, so the container can't create the files in them when the entrypoint script runs.

[ammacdonald3]

Thanks so much for the quick reply! Based on your feedback, I was able to get it running by manually copying over the sites.json file from my clean MacBook install as it was missing from my Synology install. The sites' icon files were also missing, so I copied those over too. Interestingly, the background images and the favicon file all installed correctly directly on my Synology. I also originally executed the docker compose command with sudo, so I'm not sure why I wouldn't have had permissions to create these certain objects. Closing out the issue now as it's currently working for me, but let me know if I can provide any more info about my environment in case you see this again.