Jocelyn Le Sage

The device name can already be set from the CrashPlan UI.

I think that `-v /volume1/CP-NAS-SHARE:/storage:ro` should work. What would not work is `-v /volume1:/storage:ro`. However, by using this mapping, I would not expect to see `CP-NAS-SHARE` from CrashPlan, since your...

So you just need to choose which mount to use and then make sure it is selected in CrashPlan. So if you create the container with `-v /volume1/CP-NAS-SHARE:/CP-NAS-SHARE:ro`, then in...

The version it tries to download indicate that you don't have the latest Docker image. So as suggested, updating the Docker image will fix the problem.

Yes, CrashPlan self-update is disabled (https://github.com/jlesage/docker-crashplan-pro#why-crashplan-self-update-is-disabled), so you need to update the Docker image to update CrashPlan. To automatically update containers, you can also install Watchtower (https://github.com/jlesage/docker-crashplan-pro#docker-image-update).

Can you try to perform the following action: https://github.com/jlesage/docker-crashplan-pro#device-status-is-waiting-for-connection

Can you look at `log/service.log.0`, under the folder mapped to `/config`, to see if there is any clue about the issue.

This issue comes back from time to time. So far, the solutions that worked for some are: - Clear the cache. - Reboot the host. - Restart from scratch (i.e....

I though about something else that could be tried: rename one of the following directories, one at time: - `repository` - `xdg` These folders are located under the directory that...

Could you try to have a chat with the CrashPlan support team ?