CrashPlan and CrashPlan Pro on Synology using Docker

Important Note
Code42 has removed headless functionality in the latest v6 release of CrashPlan for Small Business (formerly CrashPlan Pro). Existing docker instances may still continue to run for a while, but this ultimately marks the death of any sort of CrashPlan backup for Synology.

I recommend using BackBlaze B2 with Synology’s Cloud Sync application. There are some drawbacks (e.g. you can’t cloud sync the same folders with different services), but ultimately it is fairly priced and works well.

Archive Content:
Synology introduced Docker to the DSM in version 5+, which has opened up new ways of running some applications in Synology. Not all Synology boxes have enough resources to run docker, check if your Synology NAS can run Docker here.  Using Mike Tabor’s excellent tutorial post I was able to get CrashPlan up and running on my 713+ DiskStation. However, his tutorial only covers the basic CrashPlan application, and not CrashPlanPRO. I’ve written up a quick and dirty guide to get CrashPlan or CrashPlanPRO working on docker in Synology.

Prepare the Synology NAS for Docker

  • Login to Synology, go to Package Center
  • Uninstall CrashPlan from Package Center (if previously installed)
  • Install Docker in Package Center
  • Connect to Synology via SSH as a user with Admin privileges

Get the latest Docker Images for CrashPlan or CrashPlanPRO

First, we will pull a CrashPlan or CrashPlanPRO image from docker hub.  Note that if connected via DSM6, we will need to start the session with “sudo su”, or add “sudo” before each of the docker commands:

If using CrashPlan

If using CrashPlanPRO:

Create and run CrashPlan container using the image.

If multiple volumes need to be specified, add another -v statement after the first one e.g. “-v /volume2/:/volume2”

If using CrashPlan:

If using CrashPlanPRO:

Wait until the container has fully started up (typically less than 2 minutes)

Get the GUID from CrashPlan

In the same SSH session, enter into a bash session for the container:

The command prompt will now take place inside the container. You may see an error which is safe to ignore for now: “ERRO[0000] Unable to connect to local syslog daemon”. In the bash session, enter the following command to get the headless key

It will output something similar to the following. The first number is the port used, 4243. After the comma, the guid key is listed, then the IP for the Synology NAS. In this example below, the “4fx72835-3fcd-4319-afd5-698212c77ba7” key should be recorded to connect to the system with CrashPlan from a desktop machine


Update the workstation to connect to CrashPlan running in Docker


If using Windows, update C:\ProgramData\CrashPlan\.ui_info with the guid recorded in the command above, and the IP address of the Synology NAS. If on a Mac, the path is /Library/Application Support/CrashPlan/.ui_info.  For example:


If using Windows, update C:\Program Files\CrashPlan\conf\ and ensure serviceHost is enabled and pointing to the Synology NAS. On a Mac, this path is typically /Library/Application Support/CrashPlan/conf/.ui_info.  For example:


Connect to CrashPlan

After connecting successfully to the CrashPlan instance, adopt a previous computer (if applicable) to ensure the backup history and settings are retained.

If you have large backup sets and memory needs to be adjusted, double click the CrashPlan logo in the top right of the program and apply a custom command. In the example command below, the memory usage is increased to 2GB in order to work with very large file sets. Do not increase this value beyond what is available on the Synology NAS.  More information on this command can be found here.

java mx 2048, restart


CrashPlan on Docker can’t see my files

Sometimes the mapping for the root volume doesn’t seem to stick for sub shares in the container. To fix this, stop the container and edit it in Docker. Add each share used in CrashPlan backups to the container and mount them the same way they were referenced originally. For example, if CrashPlan backs up files on a share named “Photo” on volume1, then add that share to the container with a mount path of “/volume1/Photo”.

CrashPlan Updated to v4.8 and now my docker image is broken

The following reply by reddit user ajr6037 has a solution:

Join the Conversation


  1. Wow Chris! Thanks for sharing this.

    I got it working on my DS713+ nice and easy with your explanation ;-)

    I haven’t removed CrashPlan package from DS yet, just stopped it for now.
    Adopted existing backup and > 700GB is already up to date.

    One challenge remains however. Since docker instance runs in it’s own network segment (172.x.x.x) i’m not able to connect from a Windows PC on the LAN (192.168.123.x) to backup from Windows to DS.

    Unfortunately, i haven’t found a clear explanation yet, on how to move my Docker instance into my existing LAN :(

    But i’m really happy that i got rid from the unstable CrashPlan process on DS!



  2. Thanks so much Chris! You made this tutorial super short and sweet! Thanks for including the info for CrashplanPro as well!

  3. For CrashPlan ProE you can try using one of the other docker packages e.g. docker pull erikaulin/crashplanproe – more info here on that package: I haven’t tried it myself.

    Regarding the 172.x.x.x network, I don’t see an easy way to change this on Synology. Normally you would need to create a bridge (, but Synology doesn’t have any of those options built into the docker system running. So it would probably mean some modifications of the Synology core files, which can be problematic.

  4. Hi Chris, thanks for the response. I did find Erik’s solution right before your comment yesterday and spent most of the day and evening trying to get it working properly. The issue I ran into is exactly what you mentioned, the damn 172 network. Whether I set the port mappings in bridge or set it to use host it always grabbed the 172 network and the port mappings never worked. I saw some folks online who set up their main router to route the traffic, but we’re a school and will ideally have at least two Synologies on campus that both need to run Crashplan so that makes no sense for us. Just in case you haven’t played with it, you can still completely control docker through CLI. I did spin up some customized containers that were able to use more settings than the GUI in Synology allowed but that didn’t help me. I reached out to Synology support and am still plugging away!

  5. I am having a problem where I am doing backup between two machines on the same family account but in different locations. I am having issues where the folder I choose to save the backup is not able to be used. It just says waiting for backup.

  6. When running crashplan in docker hibernation does not work. Is there any way we can make it work?

  7. Anyone have issues where the crash plan client crashes and I think the container must have also because when I go back to the container the .ui_info has changed and it no longer has access to volume1 besides the crashplan directory?

  8. Hello,

    I appear to be running version 4.6 in my Docker container. I thought that it would auto update but it does not appear to have done so.

    Is there a easy way to upgrade it to 4.7?

  9. This was working great, but then yesterday I went to connect from my desktop with the CrashPlan client. As it loaded it put up a message that said “upgrading”. After a couple of minutes the client just disappeared from my screen. When I tried to launch it again it couldn’t connect. Looking at the container, it shows messages in the terminal indicating that the CrashPlan service has stopped.

    I tried to remove the container and then reinstall CrashPlan. Got it running and then when I tried to adopt it, had pretty much the same thing occur. The client software put up a message about “upgrading” and when it was done the CrashPlan service is stopped and inaccessible.

    Anyone else running into this? Any suggestions for a fix?

  10. My Desktop Crashplan GUI is no longer able to connect to the Docker Service running on the Synology. Looks like the container log shows the last correct startup was on 9/29. Any ideas? I tried restarting the Synology (1515+) and I tried to start and stop the docker container….no luck either way. The log is huge – it looks like the container tried to upgrade to 4.8 and maybe some java lib is failing – could failing due to bad network address? Something has definitely changed.

  11. I created a new container and installed jcrs latest docker image. It looks like docker is ok now, but I am unable to configure the service running on the Synology because of the incompatibility between the desktop gui (4.7) and the service on the NAS (4.8). Anyone know how to bump the windows rev to 4.8? I am running on windows 10 64-bit. Thanks!

  12. This looks to be a known issue. I can’t find 4.8 anywhere to download to fix it…

    Known Issues
    Computer-to-computer backups may stop if one computer upgrades to CrashPlan app version 4.8 and the other computer remains on version 4.7 or earlier. This could occur if one computer is using an unsupported operating system, such as Windows XP (which cannot be upgraded to CrashPlan app version 4.8).

  13. You can find links for all 4.8 versions on crashplan’s twitter feed. I installed 4.8 on both docker and win10, no luck for me.

  14. Hi Chris,
    After 8 months crashplan stopped in Docker (after the latest update DSM). When I go in the docker I can see the Crashplan container. When I trie to start the container it says: container does not exist.
    Any solution?

  15. Docker setup was easy and very simple to do, thanks for that. However I have an issue with the client running on Windows 10 as it is showing that the files are missing. BTW I have another machine connected as well that is showing that the files are missing too. I tried to fix it without any luck. Thanks.

  16. Any word yet on a 5.X version of CrashPlanPro that will run on Synology? Hopefully they haven’t made this impossible with the latest changes.

  17. Hi, Is the crashplan pro client identical to the new crashplan for Small Business? If not, any plans to make a crashplan for small business docker now that Crahsplan home is discontinued ?

  18. Yes, they have renamed CrashPlan Pro to CrashPlan Small Business. Thus far the backup client hasn’t changed, but I would guess there will be some modifications soon.

  19. Excellent write-up Chris.

    Is anyone else having issues with this setup in the last couple days? I’m using Windows to monitor my NAS running CP Pro and Code 42 just released a new version, 6.6 “Modern EndPoint Backup”, which it auto upgraded to.

    I spoke with tech support about it and they mentioned headless setups of CP were no longer available, so now I can’t monitor my backup.

    Supposedly CP on linux will also auto upgrade to 6.6, but I don’t know if that’s happened yet.

    Any ideas?

  20. Thanks San for the info. I had the same problem with the latest crashplanpro (I was on crashplan home till they terminated the service, now need to set up it again). So I installed CrashplanPro 4.9.0, did the same installs like before, now it keeps saying “Unable to connect to the backup engine.” Not sure how to fix it. Any suggestions?

  21. anyone ran into this error when try to start docker?

    “docker error response from daemon device or resource busy”

Leave a comment

Your email address will not be published. Required fields are marked *