Closed ridgers closed 2 years ago
Try to replace $HOME
with the actual path you want to map.
Note that /volume1
, can't be mapped directly: you need to map folders under it instead.
Thank you, I got it working again!
On May 20, 2022, at 6:37 PM, Jocelyn Le Sage @.***> wrote:
Try to replace $HOME with the actual path you want to map.
Note that /volume1, can't be mapped directly: you need to map folders under it instead.
— Reply to this email directly, view it on GitHub https://github.com/jlesage/docker-crashplan-pro/issues/376#issuecomment-1133438761, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJDNDIYBPIRGANYM66SXYW3VLAH2RANCNFSM5WQSK7PQ. You are receiving this because you authored the thread.
Great!
Hello, when creating my container, I get the above error.
This is the command I am using: sudo docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=16G -e SECURE_CONNECTION=0 -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v $HOME:/volume1:ro --restart always jlesage/crashplan-pro
Running on a Synology DS1821+ DSM 7.0.1-42218 Update 3
Docker had been working normal until about 7 days ago when Crashplan issued an update and I attempted to update the docker image.
Kind regards,