Accessing Crashplan GUI about docker-crashplan HOT 5 CLOSED

why not just access the GUI the way the README suggests? https://github.com/JrCs/docker-crashplan#access-the-gui-from-your-desktop-crashplan-application

or per CrashPlan website itself about how to use headless crashplan

from docker-crashplan.

Because both of them requires a local installation of CrashPlan as well as the container. The whole idea of having the docker container running CrashPlan is to isolate it from the host it runs on. I wanted to move my host CrashPlan server into the container to, well, contain it. It defeats the idea to have to install CrashPlan on the host for the GUI when you already have a perfectly good installation for it in the docker container. Having it both places kind of making the move into docker moot.

from docker-crashplan.

you can install the CrashPlan GUI on a different host and connect over SSH.

To each their own if this is something you need I'd say go ahead and fork / pr 👍

from docker-crashplan.

I have to say I'm a little disappointed, but I'll respect this of course. I had hoped that this would spawn some interest, spending time preparing the case and all. I know too little about X and java-debugging to get any further on my own.

Since I can't run the GUI from this container, then I'm not going to use this container anyways. It makes no sense having CrashPlan in a container when you need the same CrashPlan installation on the server host to access the GUI. And I don't want to install CrashPlan on any other machines since I cannot ask of users to have to manually edit the .ui_info file.

Over and out.

from docker-crashplan.

you need the same CrashPlan installation on the server host to access the GUI

already explained you don't need it on the server host see previous link :)

from docker-crashplan.