CrashPlan Container with CrashPlan Desktop App
To run this container, please use this command:
docker run -d --name="CrashPlan" \ --net="bridge" \ -p 4242:4242 \ -p 4243:4243 \ -p 4280:4280 \ -v "/path/to/your/crashplan/config":"/config":rw \ -v "/path/to/your/manifest/dir":"/backup":rw \ gfjardim/crashplan
###Some supported variables:
This will set the correct timezone. Set yours to avoid time related issues.
This will disable MPROTECT for grsec on Java executable (for hardened kernels).
This will enable password protection for your webui interface.
This container ports can be changed, in bridge network mode, changing the "-p" switch from the run command, or, in host mode, using variables started by "TCPPORT" prefix.
####Port 4242 (TCP_PORT_4242):
This port is used by CrashPlan for computer-to-computer backups.
-p 4242:4242 or
####Port 4243 (TCP_PORT_4243):
This port is used by CrashPlan app to connect to CrashPlan service.
-p 4243:4243 or
####Port 4280 (TCP_PORT_4280):
This port exposes a noVNC instance with the CrashPlan Desktop App.
-p 4280:4280 or
Then navigate to
http://yourip:4280/vnc.html?autoconnect=true&host=192.168.0.100&port=4280 to access the graphic user interface.
This container will automatically update to Crashplan Small Business, when you switch your account. It is Crashplan whom pushes the update, you'll have nothing to do.
Will you look to build a Crashplan Pro (Small Business) with noVNC given their announcement of terminating the home plan?
Would be really nice if you could expose Java's -Xmx flags through variables - large backup sets consume way more than 1GB. For now, editing /config/bin/run.conf to change them works.
Sorry, correction: using VNC_PASSWORD has the same effect as not setting VNC_PASSWD; any password (or none at all) works.
How are you people making password authentication work?
Even though I see in the source on github you're looking for VNC_PASSWD, I cannot login when I set that environment variable. I can access the webUI with no password.
I saw on another crashplan docker container a reference for VNC_PASSWORD so I tried it on a whim and that variable actually works and I can login with that password.
Very nice, thanks.
The web vnc interface did not work for me though, so I had to export the main vnc port. I also added my /home/username/ path so that it matched my old backup when I adopted it.
So I just added this
-p 4239:4239 \
-v "/home/username/":"/home/username":rw \
This is pretty awesome the way you set it up! Was able to replace my crashplan instance on my home server with this docker vm in less than 5 minutes, adopting my existing backup to crashplan cloud. The noVNC trick is golden here!
@psnowden Same exact thing happening to me.
I have checked the docker logs and there are some warnings and an error:
Cannot read from Windows Registry on a Linux system
Cannot write to Windows Registry on a Linux system
Encrypted Bin Pass= '**'
Encrypted Hex Pass= '**'
Warning: could not find self.pem
No installed websockify, attempting to clone websockify...
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/**:1
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
Xvnc TigerVNC 1.6.0 - built Dec 24 2015 16:05:46
Copyright (C) 1999-2015 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 11202000, The X.Org Foundation
I'm only seeing a blank black screen when I try to view the WebUI. I've restarted the docker several times and even restarted unRAID to no avail. Any suggestions?