CrashPlan-Pro Docker-Compose: Cannot start

  • Hi,

    I want to setup a Crashplan-Pro Docker. I cannot make it work.


    Here's my Docker-Compose file:

    After starting the stack, I go check the container's log:

    I guess you noticed the:

    Code
    [CrashPlanEngine] starting...,
    [CrashPlanEngine] starting...,
    [CrashPlanEngine] starting...,
    [CrashPlanEngine] starting...,
    [CrashPlanEngine] starting...,
    [CrashPlanEngine] starting...,

    If I launch the Crashplan-pro webpage I see an error message: "Code42 cannot connect to its background service" "Retry".

    Sometimes I just see the Code42 splashscreen.

    I can see that the config folder works because Crashplan creates all it's confif files and folders in there.


    If I remove one volume line (- "/srv/dev-disk-by-label-500MB/docker_crashplan:/config"), the docker starts normally and I can see the login page. It's weird.

    I've tried creating a new shared folder for the config. Same behavior.


    Any ideas how to make this work?


    Here's the Container Inspect in Attachment.

    Container_Inspect.txt

  • Hi Morlan.


    Well, if I only mount the config (and not the Media folder), Crashplan doesn't start either. Like this:

  • When you say "populate", how do I check that exactly?


    I could do this though:

    Using Windows Explorer, I did create a file, named "zoubie.txt", in the docker_crashplan folder.

    Then : crashplan-pro Container details: Console: /bin/sh: Connect

    The zoubie.txt file was there.


    The 1001:100 user is "dockeruser". It's member of users, sudo, ssh:

    uid=1001(dockeruser) gid=100(users) groups=100(users),27(sudo),115(ssh)


    When the docker_crashplan folder was created, I gave these permissions: Everyone:read/write.

    Then I did: ACL: And gave the user dockeruser Read/Write permission.

    Owner: dockeruser : Read/Write/Execute

    Group: users : Read/Write/Execute

    Others: : Read/Write/Execute

    Replace all existing permissions.

    Recursive: Apply permissions fo files and subfolders.

  • Also:

    If I SSH into the OMV I can edit the zoubie.txt file like this:

    dockeruser@omv5-vm2:/srv/dev-disk-by-label-500MB/docker_crashplan$ sudo nano zoubie.txt

    Added some text. Saved it. Re-opened it and the changes were there.


    Also did this:

    dockeruser@omv5-vm2:/srv/dev-disk-by-label-500MB/docker_crashplan$ sudo mc (midnight commander)

    I could copy the zoubie.txt file to zoubie2.txt

  • If I SSH into the OMV I can edit the zoubie.txt file like this:

    dockeruser@omv5-vm2:/srv/dev-disk-by-label-500MB/docker_crashplan$ sudo nano zoubie.txt

    Added some text. Saved it. Re-opened it and the changes were there.

    Be aware that when you use sudo with your commands you cannot catch a permission error because you are temporarily the root user and always have permission.


    Also in my opinion you have already introduced to many variables where there could be a permission issue. For example you should not fiddle with ACL unless you exactly know what you are doing. ACL's are usually not necessary unless you need to configure complex multiuser environments.


    My suggestion would be to completely remove the shared folder /srv/dev-disk-by-label-500MB/docker_crashplan. Then without recreating the folder, delete and redeploy the docker-container. Docker will automatically create the folder, if it does not exist, with the correct permissions.


    Also I think you should reconsider to remove the dockeruser from the sudo group. They main reason why we create a specific dockeruser is so that we have a relatively unprivileged user running the containers. You undermine this by enabling sudo.

  • Thanks Morlan.


    I did remove the shared folder /srv/dev-disk-by-label-500MB/docker_crashplan. I also removed dockeruser from sudo group.

    Then I created a new stack in portainer with this:

    The stack started and created the docker_crashplan folder and all it's subfolders. I was able to check it by SSHing in OMV:

    Still, Crashplan doesn't start normally. Still seeing this in the log:

    Code
    [CrashPlanEngine] starting...,
    [CrashPlanEngine] starting...,
    [CrashPlanEngine] starting...,
    [CrashPlanEngine] starting...,

    If I go on the Crashplan webpage, all I see is the Code42 splashscreen.

  • I just tried this docker-compose file and it worked.

    Code
    version: '3'
    services:
    crashplan-pro:
    image: jlesage/crashplan-pro
    ports:
    - "5800:5800"
    volumes:
    - "/home/dockeruser/appdata/crashplan:/config:rw"
    - "/media/dockeruser:/storage:ro"
  • I did create a new drive. And now it works!

    I get to the login screen of Crashplan.

    Code
    dockeruser@omv5-vm2:/srv/dev-disk-by-label-1GB$ cd docker_crashplan
    dockeruser@omv5-vm2:/srv/dev-disk-by-label-1GB/docker_crashplan$ ls
    bin cache conf cp_version log machine-id repository var xdg

    Thank you so much for the help Morlan! I really appreciate it.


    I'm currently testing a new CrashPlan installation, so I might be back with more questions.

  • I just tried this docker-compose file and it worked.

    Code
    version: '3'
    services:
    crashplan-pro:
    image: jlesage/crashplan-pro
    ports:
    - "5800:5800"
    volumes:
    - "/home/dockeruser/appdata/crashplan:/config:rw"
    - "/media/dockeruser:/storage:ro"

    Apologies for hijackin the post. Totally new to linux and docker so total noob questions.


    I would like to do the same thing as I already have a crashplan pro account. The big question for me is how:

    That is I can copy the code from above. I know enough to know how to get the PUID of the user.


    What I don't know is where to write the code/docker compose file or how to change the volumes to where my docker data is stored and what I want backed up.


    Is anyone able to do a dummys guide please. Assume I'm a complete moron:/and know nothing.


    Massive thanks for any help.:)

  • What I don't know is where to write the code/docker compose file or how to change the volumes to where my docker data is stored and what I want backed up.

    Take this as a reference

    [How-To] Nextcloud with Letsencrypt using OMV and docker-compose

    use the "CLI" version, as docker-compose version 3 will not work in Portainer


    change

    Code
    /home/dockeruser/appdata/crashplan

    to the path where you want to safe the config. Similar for the storage

  • thank you.


    Good news: docker installed - i get the crashplan login screen.

    not so good news - it wont let me log in. - I get an error "Unable to sign in can't connect to server"

  • Hi,


    I'm getting an error. Am I being an idiot?


    root@GoodStore:~# docker exec -it crashplan-pro /bin/bash

    OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

    root@GoodStore:~#

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!