How to run Crashplan in Docker on Synology NAS

Crashplan running in Docker on Synology

I am a huge fan of CrashPlan and have been using it for years on my Synology NAS using this install guide I wrote up some time ago.

Admittedly the process in the old guide wasn’t always roses. Crashplan would push out an update and that update would, at times, break the Synology Crashplan client from PC Load Letter and backups would stop running for a couple days – maybe a week. Patters being the awesome guy he is, usually updated his Synology Crashplan package quickly and all was good again.

Then last year in DSM 5.2, Synology added support for Docker which opened up the possibility to run all sorts of software in a virtual container running on your Synology NAS. One such software being Crashplan and below I’m going to show how I now have Crashplan running in Docker on my Synology DS1815+ NAS!

Getting started with Crashplan in Docker

Before we start there are a few things I’m going to assume you’ve already done, if not do them now.

  • You have a Crashplan account with the desktop client already installed, if not click here to sign up now.
  • You are using a supported Synology NAS that can run Docker and already have the package installed. If not already installed go to: Package Center > Utilities > Docker and click Install.

Now lets get started!

How to install Crashplan in Docker on Synology NAS

For this guide I’m using my Synology DS1815+ NAS running DSM 6.0-7321 Update 3.

  1. Enable SSH on your Synology, this is only temporarily, by going to: Control Panel > Terminal & SNMP > and checking “Enable SSH service“, then clicking Apply. Be sure to make note of the SSH port number, default is 22.
    Enable SSH on Synology
  2. Now SSH into your Synology using PuTTy or other terminal of your choice, using an account that has admin access.
  3. We first need to pull, or download, a Crashplan Docker container from the Docker Hub by typing the following command:
    sudo docker pull jrcs/crashplan

    Pull Crashplan Docker container
    Depending on your internet connection this might take a minute or two.

  4. Once that is finished type the following command to run the Crashplan container:
    sudo docker run -d --name Crashplan -p 4242:4242 -p 4243:4243 -v /volume1:/volume1 jrcs/crashplan:latest

    Install Crashplan docker container
    Note: If you have more volumes to backup simply add more -v as needed, like -v /volume2:/volume2 – etc.

  5. Go back to the Synology interface and go to: Docker > Container > Crashplan > Details > Terminal > Create > Bash and type the following:
    cat /var/lib/crashplan/.ui_info

    Docker crashplan ui_info

  6. Next, go to Docker > Container > Crashplan and STOP the container. Once stopped click on Edit then check “Enable auto restart” then OK and START the Crashplan container again.
    synology docker crashplan autostartThis is so that when the NAS gets restarted (think DSM upgrades) that Crashplan will auto start.
  7. Now lets edit the .ui_info file located on your computer at C:\ProgramData\CrashPlan, replacing everything that might already be listed with the output from the step above. Also edit the to the IP address of your Synology NAS. Then Save the .ui_info file, after saving it set the properties to Read-Only.
    crashplan docker ui_info
    NOTE: File location for MAC users: /Library/Application Support/CrashPlan/.ui_info
  8. Finally, edit the file located at: C:\Program Files\CrashPlan\conf and edit the second line “serviceHost” so that it points to the IP address of your Synology NAS and be sure to remove the # at the beginning.
    crashplan docker

That’s it!

Crashplan is now running in Docker on your Synology NAS and the desktop client configured and ready for you to open it and select what folder and/or files you want Crashplan to backup.

docker crashplan desktop client

If you’re wanting to learn more about Docker, I’d recommend taking a look at a course by Nigel Poulton called Docker and Containers: The Big Picture.

Enjoy and I hope this works as well for you as it has for me!

Similar Posts