p peswe peswe After I Crashplan abandoned Home Users I went for JottaCloud as a Cloud Backup/Archive. You'll have to pick another backup app and storage provider. It used to work, but it wasn't supported by Crashplan, and it was tricky to update. I'm not having issues with the applications themselves, but I assume best practice is not to run as root. Crashplan has dropped support for headless mode on a Synology NAS in the next version. For the most part, I'm just using the DSM Docker UI and not installing / starting containers via SSH. Once stopped click on Edit then check Enable auto restart then OK and START the Crashplan container again. I've tried playing with chown/chgrp on some of the folders but it doesn't seem to make a difference. Go back to the Synology interface and go to: Docker > Container > Crashplan > Details > Terminal > Create > Bash and type the following: cat /var/lib/crashplan/.uiinfo Next, go to Docker > Container > Crashplan and STOP the container. I'm currently subscribed to Crashplan Pro and from what I've gathered, I either need to use Crashplan in a docker container or via workarounds. When restarting the docker container, the logs show the GID = 100 (users group), but the UID is still showing as 0 (root). Hello, I'm thinking of getting either the 216 or the 918+ to host archived videos/photos. Following that, I switched these to the user group and a specific user (which has read / write permissions to both the docker share and my media share). When I originally created the docker applications, I was getting permission issues while setting PGID / PUID, so I initially set these to root (0/0), assuming this was necessary to create the container. Looking for some help regarding which user docker containers run as. The following Docker solution, which seems to be maintained by only one person, appears to be the only one that works currently: IMHO, it looks like a makeshift solution that may stop working if the developer decides to abandon the project.
0 kommentar(er)
