Automating Crashplan Updates

 In my previous post, I showed the run command I used to get Crashplan running on my QNAP device. Fast forward a few months and Crashplan stopped working because it looks like they have updated their app. Unfortunately, the container image cannot update itself so I wrote a script that goes through the same process described here: https://github.com/jlesage/docker-crashplan-pro#docker-image-update

#!/bin/sh

echo "========================"
echo "Updating container image"
echo "========================"

docker pull jlesage/crashplan-pro

echo "=================="
echo "Stopping container"
echo "=================="

docker stop crashplan-pro

echo "======================"
echo "Removing the container"
echo "======================"

docker rm crashplan-pro

echo "================="
echo "Run the container"
echo "================="

docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=12G -p 5800:5800 -p 5900:5900 -v /share/docker/appdata/crashplan-pro:/config:rw -v /share:/share:ro jlesage/crashplan-pro

Be sure to chmod +x the file so you can run it.

Crashplan on QNAP

Turns out there's a nice docker image that can run on QNAP, but to really use it to its full potential you can't use Container Station because it won't let you map the /share drive into the container.

I use the https://github.com/jlesage/docker-crashplan-pro image and it works wonderfully. This issue really helped: https://github.com/jlesage/docker-crashplan-pro/issues/8

The solution is to SSH into your QNAP, and manually run the docker command. Container Station will then be able to "see" your running container so you can manage it afterwards.

The command to run is:

docker run -d \

    --name=crashplan-pro \

    -e USER_ID=0 \

    -e GROUP_ID=0 \

    -e CRASHPLAN_SRV_MAX_MEM=12G \

    -p 5800:5800 \

    -p 5900:5900 \

    -v /share/docker/appdata/crashplan-pro:/config:rw \

    -v /share:/share:ro \

    jlesage/crashplan-pro