jlesage / docker-crashplan-pro

Docker container for CrashPlan PRO (aka CrashPlan for Small Business)
MIT License
295 stars 37 forks source link

Need basic help with installation - need more details #34

Open bgmess opened 6 years ago

bgmess commented 6 years ago

I am fairly new to Linux and Docker. I need more instructions that those given in the quick start:

Launch the CrashPlan PRO docker container with the following command:

docker run -d \ --name=crashplan-pro \ -p 5800:5800 \ -p 5900:5900 \ -v /docker/appdata/crashplan-pro:/config:rw \ -v $HOME:/storage:ro \ jlesage/crashplan-pro

Where do I enter the above commands?

Is this all I need to do?

Any tips would be greatly appreciated. Not sure how to begin. I have installed Docker on the Synology NAS, but that's as far as I got.

Thanks, Brian

PNMarkW2 commented 4 years ago

My CrashPlan installation on my Synology NAS has been running fine for months, actually nearly a year since my last post. Now I'm getting emails regularly that there hasn't been any backup, the email today said nothing has been backed up for 8 days.

So my first question is why would something that has been running fine for nearly a year just stop? And if it stopped because it's missing some update, why can't it tell me that instead of just stopping?

Second, when I try to bring up the local web interface I have to log in, which I do, and then I do again and again because it will sit there and say it's scanning files, then go to a black screen and sit there until asking me to log in again. This happens so quickly I'm not actually able to do anything when I get logged in, but I did get a look at the log which says there is an upgrade I need.

My guess is I have the nuke the whole thing and reinstall CrashPlan, but I wanted to check here first because that's not a process I enjoy.

Thank you for your help.

jlesage commented 4 years ago

CrashPlan will not perform any backup if its version is too old. So if you didn't upgraded your container recently, then you need to do it to re-enable backup.

If you don't want to manually bother with upgrading your container, you could try to install Watchtower (https://github.com/containrrr/watchtower), a container which allows to seamlessly upgrade your containers.

PNMarkW2 commented 4 years ago

Thank you for taking the time on a holiday to respond. I truly appreciate that, and I'll look into what you suggested since my efforts to follow the directions to update always seem to result in grief.

I will say again if the reason for the program to stop working is known, such as a version is too old, that perhaps that should be explicitly reported along with the email saying that the backup hasn't happened.

Thank you again.

Mark

jlesage commented 4 years ago

I will say again if the reason for the program to stop working is known, such as a version is too old, that perhaps that should be explicitly reported along with the email saying that the backup hasn't happened.

You should forward this feedback to CrashPlan, since there is nothing I can do for that...

SJLBoulder commented 4 years ago

PNMarkW2 - I have a suggestion for your notification problem. You can join GitHub and "watch" jlesage's project for updates, e.g. a new Docker container with the latest CrashPlan version. Go here, and click on "watch" at the top of the page: https://github.com/jlesage/docker-crashplan-pro