Hi there,
I was having some hard time creating a CrashPlan Pro docker. CrashPlan would start. I've troubleshooted and found that if I didn't specify any Volumes in the Compose file, CrashPlan would start OK. Good.
Then I've tried specifying a storage volume. It works. Crashplan starts. It created it's own config folder here by itself:
/var/lib/docker/volumes/4345af57db0eb193671b1872ec653b97e1d553332ca0c8460019a6bb01ab26de/_data
But If I try to specify the /config volume, CrashPlan doesn't start.
So this works:
version: "2"
services:
crashplan-pro:
hostname: docker-crashplan-OMV
container_name: crashplan-pro
image: jlesage/crashplan-pro
environment:
- "USER_ID=2028"
- "GROUP_ID=100"
ports:
- "5800:5800"
volumes:
- "/srv/dev-disk-by-label-NVMe500GB:/storage"
Alles anzeigen
But this doesn't work (only difference is the additional volume):
version: "2"
services:
crashplan-pro:
hostname: docker-crashplan-OMV
container_name: crashplan-pro
image: jlesage/crashplan-pro
environment:
- "USER_ID=2028"
- "GROUP_ID=100"
ports:
- "5800:5800"
volumes:
- "/srv/dev-disk-by-label-NVMe500GB:/storage"
- "/srv/dev-disk-by-label-NVMe500GB/Settings/CrashplanPro_Docker:/config"
Alles anzeigen
I didn't create the ../Settings/CrashplanPro_Docker folder at first. I wanted docker to create it by itself. Which it did. But CrashPlan doesn't want to start.
At the end of the log, we see:
[CrashPlanEngine] starting...,
[CrashPlanEngine] starting...,
[CrashPlanEngine] starting...,
[CrashPlanEngine] starting...,
[CrashPlanEngine] starting...,
[CrashPlanEngine] starting...,
Any ideas why this wouldn't work?