Also adjust the memory limit, if necessary. Note: I have updated to QTS 4.2.2 and running the crashplan container without the -net host option still does not work.Īfter the update, you may want to open the ContainerStation app in the QNAP admin interface and verify that the “Auto start” option is enabled for the new crashplan docker image. As the CrashPlan configuration files are stored outside the docker container, the new instance will pickup the existing configuration and needs no further adjustment. That’s about it! Now you have an updated CrashPlan container running on your NAS. # check if it is running (after some minutes)ĭocker exec crashplan /etc/init.d/crashplan status 1 - Setting up QNAP NAS with CrashPlan TechnoElectroTV 12 subscribers Subscribe 18K views 8 years ago This videos shows how to set up CrashPlan on a QNAP 419 P II NAS device. volume /share/CACHEDEV1_DATA/Containers/crashplan/config:/var/crashplan \ # update the docker image to the latest versionĭocker run -d -name crashplan -e TZ -publish 4242:4242 -publish 4243:4243 -net host \ Then, update the container as follows (learn more about existing docker container upgrades): To update the Crashplan docker instance, hop on your favorite shell and ssh. The third step is detailed in the following section. The first two steps are easily done from within the QNAP admin interface. ![]() Make sure that you are running the latest version of the ContainerStation. Update all apps from within the QNAP app store.The steps I took to update Crashplan are the following: ![]() The update involved some steps, but with the Docker setup in place, the update was really easy. Much to my delight, the update went very smooth and CrashPlan works properly as expected. As in the meantime there were a lot of updates available for all moving parts, it was certainly time to update. Some time ago I installed Crashplan on my QNAP NAS with Docker.
0 Comments
Leave a Reply. |