No files shown in folders mounted from NAS

metastatic commented 6 years ago

Hi

I successfully downloaded and setup last month. However, since restarting my NAS (Synology DS415+) the other day the docker can see the shares but does not show any files in them, which means nothing is being backed up.

This is the command I used to setup-:

docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=4096M -e SECURE_CONNECTION=1 -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro -v /volumeUSB1/usbshare1-2/:/volumeUSB1/usbshare1-2:rw jlesage/crashplan-pro

Can you please assist in resolving this issue?

Thanks

Mark

jlesage commented 6 years ago

Do you see your files if you list them using:

docker exec crashplan-pro ls -l /volume1/

metastatic commented 6 years ago

Thanks for your reply. It returns 'total 0'. To answer your question, no I do not.

jlesage commented 6 years ago

What is the output of:

docker inspect crashplan-pro

metastatic commented 6 years ago

[ { "Id": "748e66b6be3b8c79a60796ac0bac2857f1759c2a15a32e2a8a2f14304615700e", "Created": "2018-01-04T19:11:41.331121196Z", "Path": "/init", "Args": [], "State": { "Status": "running", "Running": true, "Paused": false, "Restarting": false, "OOMKilled": false, "Dead": false, "Pid": 8198, "ExitCode": 0, "Error": "", "StartedAt": "2018-01-30T20:20:50.286494799Z", "FinishedAt": "2018-01-30T20:20:32.754355486Z" }, "Image": "sha256:8b5d2bf6e2628b193d055f6db43968477a86db6f77a14e2f9c35d16cc1a429e8", "ResolvConfPath": "/volume1/@docker/containers/748e66b6be3b8c79a60796ac0bac2857f1759c2a15a32e2a8a2f14304615700e/resolv.conf", "HostnamePath": "/volume1/@docker/containers/748e66b6be3b8c79a60796ac0bac2857f1759c2a15a32e2a8a2f14304615700e/hostname", "HostsPath": "/volume1/@docker/containers/748e66b6be3b8c79a60796ac0bac2857f1759c2a15a32e2a8a2f14304615700e/hosts", "LogPath": "/volume1/@docker/containers/748e66b6be3b8c79a60796ac0bac2857f1759c2a15a32e2a8a2f14304615700e/log.db", "Name": "/crashplan-pro", "RestartCount": 0, "Driver": "aufs", "MountLabel": "", "ProcessLabel": "", "AppArmorProfile": "", "ExecIDs": null, "HostConfig": { "Binds": [ "/volume1/docker/appdata/crashplan-pro:/config:rw", "/volumeUSB1/usbshare1-2/:/volumeUSB1/usbshare1-2:rw" ], "ContainerIDFile": "", "LogConfig": { "Type": "db", "Config": {} }, "NetworkMode": "bridge", "PortBindings": { "5800/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "5800" } ] }, "RestartPolicy": { "Name": "", "MaximumRetryCount": 0 }, "AutoRemove": false, "VolumeDriver": "", "VolumesFrom": null, "CapAdd": null, "CapDrop": null, "Dns": [], "DnsOptions": [], "DnsSearch": [], "ExtraHosts": null, "GroupAdd": null, "IpcMode": "", "Cgroup": "", "Links": null, "OomScoreAdj": 0, "PidMode": "", "Privileged": false, "PublishAllPorts": false, "ReadonlyRootfs": false, "SecurityOpt": null, "StorageOpt": null, "UTSMode": "", "UsernsMode": "", "ShmSize": 67108864, "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "LANG=en_US.UTF-8", "S6_BEHAVIOUR_IF_STAGE2_FAILS=3", "S6_SERVICE_DEPS=1", "USER_ID=0", "GROUP_ID=0", "APP_NAME=CrashPlan for Small Business", "APP_USER=app", "XDG_DATA_HOME=/config/xdg/data", "XDG_CONFIG_HOME=/config/xdg/config", "XDG_CACHE_HOME=/config/xdg/cache", "DISPLAY=:0", "DISPLAY_WIDTH=1280", "DISPLAY_HEIGHT=768", "S6_WAIT_FOR_SERVICE_MAXTIME=10000", "KEEP_GUIAPP_RUNNING=1", "CRASHPLAN_DIR=/usr/local/crashplan", "JAVACOMMON=/usr/local/crashplan/jre/bin/java", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1", "USER_ID=0", "GROUP_ID=0", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1" ], "Override": true, "ConsoleSize": [ 0, 0 ], "Isolation": "", "CpuShares": 50, "Memory": 0, "CgroupParent": "", "BlkioWeight": 0, "BlkioWeightDevice": null, "BlkioDeviceReadBps": null, "BlkioDeviceWriteBps": null, "BlkioDeviceReadIOps": null, "BlkioDeviceWriteIOps": null, "CpuPeriod": 0, "CpuQuota": 0, "CpusetCpus": "", "CpusetMems": "", "Devices": [], "DiskQuota": 0, "KernelMemory": 0, "MemoryReservation": 0, "MemorySwap": 0, "MemorySwappiness": -1, "OomKillDisable": false, "PidsLimit": 0, "Ulimits": null, "CpuCount": 0, "CpuPercent": 0, "BlkioIOps": 0, "BlkioBps": 0, "SandboxSize": 0 }, "GraphDriver": { "Name": "aufs", "Data": null }, "SynoUpTime": 1517343650, "SynoFinishTime": -1, "SynoStatus": "running", "Mounts": [ { "Name": "d24a6202d0e86c394eda7e3a8469f81c10c6b89d4d5976193a6cb5de9d4c143f", "Source": "/volume1/@docker/volumes/d24a6202d0e86c394eda7e3a8469f81c10c6b89d4d5976193a6cb5de9d4c143f/_data", "Destination": "/storage", "Driver": "local", "Mode": "", "RW": true, "Propagation": "" }, { "Source": "/volume1/docker/appdata/crashplan-pro", "Destination": "/config", "Mode": "rw", "RW": true, "Propagation": "rprivate" }, { "Source": "/volumeUSB1/usbshare1-2", "Destination": "/volumeUSB1/usbshare1-2", "Mode": "rw", "RW": true, "Propagation": "rprivate" } ], "Config": { "Hostname": "748e66b6be3b", "Domainname": "", "User": "", "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "ExposedPorts": { "5800/tcp": {}, "5900/tcp": {} }, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "LANG=en_US.UTF-8", "S6_BEHAVIOUR_IF_STAGE2_FAILS=3", "S6_SERVICE_DEPS=1", "USER_ID=0", "GROUP_ID=0", "APP_NAME=CrashPlan for Small Business", "APP_USER=app", "XDG_DATA_HOME=/config/xdg/data", "XDG_CONFIG_HOME=/config/xdg/config", "XDG_CACHE_HOME=/config/xdg/cache", "DISPLAY=:0", "DISPLAY_WIDTH=1280", "DISPLAY_HEIGHT=768", "S6_WAIT_FOR_SERVICE_MAXTIME=10000", "KEEP_GUIAPP_RUNNING=1", "CRASHPLAN_DIR=/usr/local/crashplan", "JAVACOMMON=/usr/local/crashplan/jre/bin/java", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1" ], "Cmd": [ "/init" ], "Image": "jlesage/crashplan-pro", "Volumes": { "/config": {}, "/storage": {} }, "WorkingDir": "/tmp", "Entrypoint": null, "OnBuild": null, "Labels": { "org.label-schema.description": "Docker container for CrashPlan PRO", "org.label-schema.name": "crashplan-pro", "org.label-schema.schema-version": "1.0", "org.label-schema.vcs-url": "https://github.com/jlesage/docker-crashplan-pro", "org.label-schema.version": "2.0.2" }, "DDSM": false }, "NetworkSettings": { "Bridge": "", "SandboxID": "99cc0c674ad8ee968ef1127e8898f933929316f894f5968b3c73e9c04dfbb8bd", "HairpinMode": false, "LinkLocalIPv6Address": "", "LinkLocalIPv6PrefixLen": 0, "Ports": { "5800/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "5800" } ], "5900/tcp": null }, "SandboxKey": "/var/run/docker/netns/99cc0c674ad8", "SecondaryIPAddresses": null, "SecondaryIPv6Addresses": null, "EndpointID": "a0c4811e51af6f7a040580ad7d48cc5187f0a36ac005a7af04e138c76a3b96d2", "Gateway": "172.17.0.1", "GlobalIPv6Address": "fe80::242:ac11:2", "GlobalIPv6PrefixLen": 64, "IPAddress": "172.17.0.2", "IPPrefixLen": 16, "IPv6Gateway": "fe80::1", "MacAddress": "02:42:ac:11:00:02", "Networks": { "bridge": { "IPAMConfig": null, "Links": null, "Aliases": null, "NetworkID": "66a9020d00442c48cd850922ce06b6dba9f18361757c517c8b2c05ea463a5ade", "EndpointID": "a0c4811e51af6f7a040580ad7d48cc5187f0a36ac005a7af04e138c76a3b96d2", "Gateway": "172.17.0.1", "IPAddress": "172.17.0.2", "IPPrefixLen": 16, "IPv6Gateway": "fe80::1", "GlobalIPv6Address": "fe80::242:ac11:2", "GlobalIPv6PrefixLen": 64, "MacAddress": "02:42:ac:11:00:02" } } } } ]

jlesage commented 6 years ago

Where are you expecting your files to be inside the container? The result of docker inspect doesn't seems to fit with the docker run command you provided.

According to docker inspect, the following container directories are mapped: /config, /storage and /volumeUSB1/usbshare1-2.

metastatic commented 6 years ago

All the shares are on /volume1 The directory /volumeUSB1/usbshare1-2 is used as a second backup destination.

What can I do to resolve this issue?

jlesage commented 6 years ago

You need to stop and remove the container and re-create it. Not sure if you are working from the shell or with the UI, but from the shell:

docker stop crashplan-pro
docker rm crashplan-pro
docker run [...]

You can take the opportunity to update the image. Before running the docker run command, pull the latest image:

docker pull jlesage/crashplan-pro

metastatic commented 6 years ago

Ok. I entered the following commands in the shell-:

sudo su - docker stop crashplan-pro docker rm crashplan-pro docker pull jlesage/crashplan-pro docker run [...]

All working well so far. However, would you mind leaving the issue open, as I'm going to wait for Crashplan to finish scanning the backup selection? As soon as it has finished I will restart the NAS and see if the container can still access /volume1

Many thanks for your assistance so far.

metastatic commented 6 years ago

Everything worked nicely until I restarted the NAS. Now the same issue has occurred. Here's the output from running the command-: docker inspect crashplan-pro

[ { "Id": "65788fa461a9917ad145be4cdd35e142a2a2a9ab6959896edee5db3a185ca704" , "Created": "2018-02-01T18:36:27.877726615Z", "Path": "/init", "Args": [], "State": { "Status": "running", "Running": true, "Paused": false, "Restarting": false, "OOMKilled": false, "Dead": false, "Pid": 12589, "ExitCode": 0, "Error": "", "StartedAt": "2018-02-05T21:39:42.943186758Z", "FinishedAt": "2018-02-05T21:37:22.851123155Z" }, "Image": "sha256:7234b96df02a1ffa3c8e0f308fce108b791ed2d9e925dd316f1c117 779795429", "ResolvConfPath": "/volume1/@docker/containers/65788fa461a9917ad145be4cd d35e142a2a2a9ab6959896edee5db3a185ca704/resolv.conf", "HostnamePath": "/volume1/@docker/containers/65788fa461a9917ad145be4cdd3 5e142a2a2a9ab6959896edee5db3a185ca704/hostname", "HostsPath": "/volume1/@docker/containers/65788fa461a9917ad145be4cdd35e1 42a2a2a9ab6959896edee5db3a185ca704/hosts", "LogPath": "/volume1/@docker/containers/65788fa461a9917ad145be4cdd35e142 a2a2a9ab6959896edee5db3a185ca704/log.db", "Name": "/crashplan-pro", "RestartCount": 0, "Driver": "aufs", "MountLabel": "", "ProcessLabel": "", "AppArmorProfile": "", "ExecIDs": null, "HostConfig": { "Binds": [ "/volume1/docker/appdata/crashplan-pro:/config:rw", "/volumeUSB1/usbshare1-2/:/volumeUSB1/usbshare1-2:rw" ], "ContainerIDFile": "", "LogConfig": { "Type": "db", "Config": {} }, "NetworkMode": "bridge", "PortBindings": { "5800/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "5800" } ] }, "RestartPolicy": { "Name": "", "MaximumRetryCount": 0 }, "AutoRemove": false, "VolumeDriver": "", "VolumesFrom": null, "CapAdd": null, "CapDrop": null, "Dns": [], "DnsOptions": [], "DnsSearch": [], "ExtraHosts": null, "GroupAdd": null, "IpcMode": "", "Cgroup": "", "Links": null, "OomScoreAdj": 0, "PidMode": "", "Privileged": false, "PublishAllPorts": false, "ReadonlyRootfs": false, "SecurityOpt": null, "StorageOpt": null, "UTSMode": "", "UsernsMode": "", "ShmSize": 67108864, "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/b in", "LANG=en_US.UTF-8", "S6_BEHAVIOUR_IF_STAGE2_FAILS=3", "S6_SERVICE_DEPS=1", "USER_ID=0", "GROUP_ID=0", "APP_NAME=CrashPlan for Small Business", "APP_USER=app", "XDG_DATA_HOME=/config/xdg/data", "XDG_CONFIG_HOME=/config/xdg/config", "XDG_CACHE_HOME=/config/xdg/cache", "DISPLAY=:0", "DISPLAY_WIDTH=1280", "DISPLAY_HEIGHT=768", "S6_WAIT_FOR_SERVICE_MAXTIME=10000", "KEEP_GUIAPP_RUNNING=1", "CRASHPLAN_DIR=/usr/local/crashplan", "JAVACOMMON=/usr/local/crashplan/jre/bin/java", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1", "USER_ID=0", "GROUP_ID=0", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1" ], "Override": true, "ConsoleSize": [ 0, 0 ], "Isolation": "", "CpuShares": 50, "Memory": 0, "CgroupParent": "", "BlkioWeight": 0, "BlkioWeightDevice": null, "BlkioDeviceReadBps": null, "BlkioDeviceWriteBps": null, "BlkioDeviceReadIOps": null, "BlkioDeviceWriteIOps": null, "CpuPeriod": 0, "CpuQuota": 0, "CpusetCpus": "", "CpusetMems": "", "Devices": [], "DiskQuota": 0, "KernelMemory": 0, "MemoryReservation": 0, "MemorySwap": 0, "MemorySwappiness": -1, "OomKillDisable": false, "PidsLimit": 0, "Ulimits": null, "CpuCount": 0, "CpuPercent": 0, "BlkioIOps": 0, "BlkioBps": 0, "SandboxSize": 0 }, "GraphDriver": { "Name": "aufs", "Data": null }, "SynoUpTime": 1517866782, "SynoFinishTime": -1, "SynoStatus": "running", "Mounts": [ { "Name": "4ad1b3b33d7be916c6ef3cc064304f313ca5ae488077b3395645c2a 47057b177", "Source": "/volume1/@docker/volumes/4ad1b3b33d7be916c6ef3cc06430 4f313ca5ae488077b3395645c2a47057b177/_data", "Destination": "/storage", "Driver": "local", "Mode": "", "RW": true, "Propagation": "" }, { "Source": "/volume1/docker/appdata/crashplan-pro", "Destination": "/config", "Mode": "rw", "RW": true, "Propagation": "rprivate" }, { "Source": "/volumeUSB1/usbshare1-2", "Destination": "/volumeUSB1/usbshare1-2", "Mode": "rw", "RW": true, "Propagation": "rprivate" } ], "Config": { "Hostname": "65788fa461a9", "Domainname": "", "User": "", "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "ExposedPorts": { "5800/tcp": {}, "5900/tcp": {} }, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/b in", "LANG=en_US.UTF-8", "S6_BEHAVIOUR_IF_STAGE2_FAILS=3", "S6_SERVICE_DEPS=1", "USER_ID=0", "GROUP_ID=0", "APP_NAME=CrashPlan for Small Business", "APP_USER=app", "XDG_DATA_HOME=/config/xdg/data", "XDG_CONFIG_HOME=/config/xdg/config", "XDG_CACHE_HOME=/config/xdg/cache", "DISPLAY=:0", "DISPLAY_WIDTH=1280", "DISPLAY_HEIGHT=768", "S6_WAIT_FOR_SERVICE_MAXTIME=10000", "KEEP_GUIAPP_RUNNING=1", "CRASHPLAN_DIR=/usr/local/crashplan", "JAVACOMMON=/usr/local/crashplan/jre/bin/java", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1" ], "Cmd": [ "/init" ], "Image": "jlesage/crashplan-pro", "Volumes": { "/config": {}, "/storage": {} }, "WorkingDir": "/tmp", "Entrypoint": null, "OnBuild": null, "Labels": { "org.label-schema.description": "Docker container for CrashPlan PRO", "org.label-schema.name": "crashplan-pro", "org.label-schema.schema-version": "1.0", "org.label-schema.vcs-url": "https://github.com/jlesage/docker-c rashplan-pro", "org.label-schema.version": "2.1.1" }, "DDSM": false }, "NetworkSettings": { "Bridge": "", "SandboxID": "4ba2a1056a71d1c28d539272589e7410dbda09043cbb7b8feba12e edf0d83318", "HairpinMode": false, "LinkLocalIPv6Address": "", "LinkLocalIPv6PrefixLen": 0, "Ports": { "5800/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "5800" } ], "5900/tcp": null }, "SandboxKey": "/var/run/docker/netns/4ba2a1056a71", "SecondaryIPAddresses": null, "SecondaryIPv6Addresses": null, "EndpointID": "c55bddf180f447f9f4c3cdf2110c942d3969fd3d79469cf4baffc 1203cb061d8", "Gateway": "172.17.0.1", "GlobalIPv6Address": "fe80::242:ac11:2", "GlobalIPv6PrefixLen": 64, "IPAddress": "172.17.0.2", "IPPrefixLen": 16, "IPv6Gateway": "fe80::1", "MacAddress": "02:42:ac:11:00:02", "Networks": { "bridge": { "IPAMConfig": null, "Links": null, "Aliases": null, "NetworkID": "e6bd44a6169efe54b96668c61df1b8ab418c59668af349 b43b6b1a92a0b7f50e", "EndpointID": "c55bddf180f447f9f4c3cdf2110c942d3969fd3d79469 cf4baffc1203cb061d8", "Gateway": "172.17.0.1", "IPAddress": "172.17.0.2", "IPPrefixLen": 16, "IPv6Gateway": "fe80::1", "GlobalIPv6Address": "fe80::242:ac11:2", "GlobalIPv6PrefixLen": 64, "MacAddress": "02:42:ac:11:00:02" } } } } ]

jlesage commented 6 years ago

If you run the docker run command by hand, don't you need to do the same thing after a restart? Looks like that after a restart a different docker runcommand is executed.

metastatic commented 6 years ago

What command do I use to start the container via the command line? When I entered the command used previously it returned-:

docker: Error response from daemon: Conflict. The name "/crashplan-pro" is alrea dy in use by container 65788fa461a9917ad145be4cdd35e142a2a2a9ab6959896edee5db3a1 85ca704. You have to remove (or rename) that container to be able to reuse that name..

metastatic commented 6 years ago

An alternative option is to start the container via the Docker package I installed on the DS415+. From there I can also modify the configuration of the container. However, the same issue still occurs.

metastatic commented 6 years ago

I just tried to run the container using the following command-:

docker run jlesage/crashplan-pro

However, that resulted in a container called mad_saha to be created. What is that all about?

bigtfromaz commented 6 years ago

Metastic,

I am writing up some notes that I think will help. I will send them in a few minutes.

From: metastatic [mailto:notifications@github.com] Sent: Monday, February 5, 2018 2:47 PM To: jlesage/docker-crashplan-pro docker-crashplan-pro@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [jlesage/docker-crashplan-pro] No files shown in folders mounted from NAS (#44)

Everything worked nicely until I restarted the NAS. Now the same issue has occurred. Here's the output from running the command-: docker inspect crashplan-pro

[ { "Id": "65788fa461a9917ad145be4cdd35e142a2a2a9ab6959896edee5db3a185ca704" , "Created": "2018-02-01T18:36:27.877726615Z", "Path": "/init", "Args": [], "State": { "Status": "running", "Running": true, "Paused": false, "Restarting": false, "OOMKilled": false, "Dead": false, "Pid": 12589, "ExitCode": 0, "Error": "", "StartedAt": "2018-02-05T21:39:42.943186758Z", "FinishedAt": "2018-02-05T21:37:22.851123155Z" }, "Image": "sha256:7234b96df02a1ffa3c8e0f308fce108b791ed2d9e925dd316f1c117 779795429", "ResolvConfPath": "/volume1//65788fa461a9917ad145be4cd d35e142a2a2a9ab6959896edee5db3a185ca704/resolv.conf", "HostnamePath": "/volume1//65788fa461a9917ad145be4cdd3 5e142a2a2a9ab6959896edee5db3a185ca704/hostname", "HostsPath": "/volume1//65788fa461a9917ad145be4cdd35e1 42a2a2a9ab6959896edee5db3a185ca704/hosts", "LogPath": "/volume1//65788fa461a9917ad145be4cdd35e142 a2a2a9ab6959896edee5db3a185ca704/log.db", "Name": "/crashplan-pro", "RestartCount": 0, "Driver": "aufs", "MountLabel": "", "ProcessLabel": "", "AppArmorProfile": "", "ExecIDs": null, "HostConfig": { "Binds": [ "/volume1/docker/appdata/crashplan-pro:/config:rw", "/volumeUSB1/usbshare1-2/:/volumeUSB1/usbshare1-2:rw" ], "ContainerIDFile": "", "LogConfig": { "Type": "db", "Config": {} }, "NetworkMode": "bridge", "PortBindings": { "5800/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "5800" } ] }, "RestartPolicy": { "Name": "", "MaximumRetryCount": 0 }, "AutoRemove": false, "VolumeDriver": "", "VolumesFrom": null, "CapAdd": null, "CapDrop": null, "Dns": [], "DnsOptions": [], "DnsSearch": [], "ExtraHosts": null, "GroupAdd": null, "IpcMode": "", "Cgroup": "", "Links": null, "OomScoreAdj": 0, "PidMode": "", "Privileged": false, "PublishAllPorts": false, "ReadonlyRootfs": false, "SecurityOpt": null, "StorageOpt": null, "UTSMode": "", "UsernsMode": "", "ShmSize": 67108864, "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/b in", "LANG=en_US.UTF-8", "S6_BEHAVIOUR_IF_STAGE2_FAILS=3", "S6_SERVICE_DEPS=1", "USER_ID=0", "GROUP_ID=0", "APP_NAME=CrashPlan for Small Business", "APP_USER=app", "XDG_DATA_HOME=/config/xdg/data", "XDG_CONFIG_HOME=/config/xdg/config", "XDG_CACHE_HOME=/config/xdg/cache", "DISPLAY=:0", "DISPLAY_WIDTH=1280", "DISPLAY_HEIGHT=768", "S6_WAIT_FOR_SERVICE_MAXTIME=10000", "KEEP_GUIAPP_RUNNING=1", "CRASHPLAN_DIR=/usr/local/crashplan", "JAVACOMMON=/usr/local/crashplan/jre/bin/java", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1", "USER_ID=0", "GROUP_ID=0", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1" ], "Override": true, "ConsoleSize": [ 0, 0 ], "Isolation": "", "CpuShares": 50, "Memory": 0, "CgroupParent": "", "BlkioWeight": 0, "BlkioWeightDevice": null, "BlkioDeviceReadBps": null, "BlkioDeviceWriteBps": null, "BlkioDeviceReadIOps": null, "BlkioDeviceWriteIOps": null, "CpuPeriod": 0, "CpuQuota": 0, "CpusetCpus": "", "CpusetMems": "", "Devices": [], "DiskQuota": 0, "KernelMemory": 0, "MemoryReservation": 0, "MemorySwap": 0, "MemorySwappiness": -1, "OomKillDisable": false, "PidsLimit": 0, "Ulimits": null, "CpuCount": 0, "CpuPercent": 0, "BlkioIOps": 0, "BlkioBps": 0, "SandboxSize": 0 }, "GraphDriver": { "Name": "aufs", "Data": null }, "SynoUpTime": 1517866782, "SynoFinishTime": -1, "SynoStatus": "running", "Mounts": [ { "Name": "4ad1b3b33d7be916c6ef3cc064304f313ca5ae488077b3395645c2a 47057b177", "Source": "/volume1//4ad1b3b33d7be916c6ef3cc06430 4f313ca5ae488077b3395645c2a47057b177/_data", "Destination": "/storage", "Driver": "local", "Mode": "", "RW": true, "Propagation": "" }, { "Source": "/volume1/docker/appdata/crashplan-pro", "Destination": "/config", "Mode": "rw", "RW": true, "Propagation": "rprivate" }, { "Source": "/volumeUSB1/usbshare1-2", "Destination": "/volumeUSB1/usbshare1-2", "Mode": "rw", "RW": true, "Propagation": "rprivate" } ], "Config": { "Hostname": "65788fa461a9", "Domainname": "", "User": "", "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "ExposedPorts": { "5800/tcp": {}, "5900/tcp": {} }, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/b in", "LANG=en_US.UTF-8", "S6_BEHAVIOUR_IF_STAGE2_FAILS=3", "S6_SERVICE_DEPS=1", "USER_ID=0", "GROUP_ID=0", "APP_NAME=CrashPlan for Small Business", "APP_USER=app", "XDG_DATA_HOME=/config/xdg/data", "XDG_CONFIG_HOME=/config/xdg/config", "XDG_CACHE_HOME=/config/xdg/cache", "DISPLAY=:0", "DISPLAY_WIDTH=1280", "DISPLAY_HEIGHT=768", "S6_WAIT_FOR_SERVICE_MAXTIME=10000", "KEEP_GUIAPP_RUNNING=1", "CRASHPLAN_DIR=/usr/local/crashplan", "JAVACOMMON=/usr/local/crashplan/jre/bin/java", "CRASHPLAN_SRV_MAX_MEM=4096M", "SECURE_CONNECTION=1" ], "Cmd": [ "/init" ], "Image": "jlesage/crashplan-pro", "Volumes": { "/config": {}, "/storage": {} }, "WorkingDir": "/tmp", "Entrypoint": null, "OnBuild": null, "Labels": { "org.label-schema.description": "Docker container for CrashPlan PRO", "org.label-schema.name": "crashplan-pro", "org.label-schema.schema-version": "1.0", "org.label-schema.vcs-url": "https://github.com/jlesage/docker-c rashplan-prohttps://github.com/jlesage/docker-c%20rashplan-pro", "org.label-schema.version": "2.1.1" }, "DDSM": false }, "NetworkSettings": { "Bridge": "", "SandboxID": "4ba2a1056a71d1c28d539272589e7410dbda09043cbb7b8feba12e edf0d83318", "HairpinMode": false, "LinkLocalIPv6Address": "", "LinkLocalIPv6PrefixLen": 0, "Ports": { "5800/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "5800" } ], "5900/tcp": null }, "SandboxKey": "/var/run/docker/netns/4ba2a1056a71", "SecondaryIPAddresses": null, "SecondaryIPv6Addresses": null, "EndpointID": "c55bddf180f447f9f4c3cdf2110c942d3969fd3d79469cf4baffc 1203cb061d8", "Gateway": "172.17.0.1", "GlobalIPv6Address": "fe80::242:ac11:2", "GlobalIPv6PrefixLen": 64, "IPAddress": "172.17.0.2", "IPPrefixLen": 16, "IPv6Gateway": "fe80::1", "MacAddress": "02:42:ac:11:00:02", "Networks": { "bridge": { "IPAMConfig": null, "Links": null, "Aliases": null, "NetworkID": "e6bd44a6169efe54b96668c61df1b8ab418c59668af349 b43b6b1a92a0b7f50e", "EndpointID": "c55bddf180f447f9f4c3cdf2110c942d3969fd3d79469 cf4baffc1203cb061d8", "Gateway": "172.17.0.1", "IPAddress": "172.17.0.2", "IPPrefixLen": 16, "IPv6Gateway": "fe80::1", "GlobalIPv6Address": "fe80::242:ac11:2", "GlobalIPv6PrefixLen": 64, "MacAddress": "02:42:ac:11:00:02" } } } } ]

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-crashplan-pro/issues/44#issuecomment-363232280, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHjxRqV1PLf7J35q-qTALyBkBtc1Jl2Aks5tR3bFgaJpZM4Ry9AV.

bigtfromaz commented 6 years ago

I just sent a note to metastaic. If he defines the container using the Synology configuration tool, the Synology will start the container after a reboot. One of the reasons to buy a Synology box is for the tooling. I always find it amazing when people buy a friendly box and then go out of their way to make it complicated. The folks over at Synology really know Linux and their configuration tooling almost always follows best practice.

From: Jocelyn Le Sage [mailto:notifications@github.com] Sent: Monday, February 5, 2018 3:00 PM To: jlesage/docker-crashplan-pro docker-crashplan-pro@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [jlesage/docker-crashplan-pro] No files shown in folders mounted from NAS (#44)

If you run the docker run command by hand, don't you need to do the same thing after a restart? Looks like that after a restart a different docker runcommand is executed. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-crashplan-pro/issues/44#issuecomment-363235653, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHjxRi9A_TknopjsKOj7ZxIOADP3HXG0ks5tR3nVgaJpZM4Ry9AV. [Image]

metastatic commented 6 years ago

@bigtfromaz Thanks for you input.

What do you mean if I define the container using the Synology configuration tool? From the posts I've read on PC Load Letter the container has to be created from the command line to specify the /volume1 mapping, as the GUI won’t let you define volume mappings at that level. Subsequently one can control it from the GUI like any other container. However, I have found that after restarting the NAS, the container auto-starts (good), but it appears it cannot access volume 1.

See the post by Jon Etkins at December 21, 2017 at 20:58-:

metastatic commented 6 years ago

[(https://pcloadletter.co.uk/2012/01/30/crashplan-syno-package/comment-page-51/#comments)]

excalibr18 commented 6 years ago

@metastatic & @bigtfromaz : RE the restarting after a reboot, you can also instruct the Container to automatically restart after a reboot from within the Synology Docker GUI after you set it up from the command line by doing the following:

Make sure the Container is stopped:
Select the Container and click the 'Edit' button.
Check the 'Enable auto-restart' option under 'General Settings'.

RE Volume1 not mounting after a reboot, I'm also a Synology user and initially set up the container via the command line. I haven't experienced any issues with Volume1 not mounting after a reboot (even when the container restarts automatically), however I don't have any external disks attached to my Synology or any other volumes mapped for this container other than Volume1.

metastatic commented 6 years ago

@excalibr18 Thanks for your input. The container automatically starts even with the "Enable auto-restart" unchecked. The issue is not with access to the external USB drive, but /volume1

excalibr18 commented 6 years ago

Sorry, at a loss then since my /Volume1 mapping persists between reboots.

Just a thought: Have you tried setting -e USER_ID=0 -e GROUP_ID=0 to match the login you use when accessing DSM, instead of leaving it with =0?

Follow jlesage's instructions at the link below to determine the value of uid and gid.: https://github.com/jlesage/docker-crashplan-pro#usergroup-ids

Tek4 commented 6 years ago

I experienced the "no files shown" problem due to a user/group permissions issue.

SOLUTION: I had to diverge from the advice in README.md which was incorrect in my case as to the GROUP_ID setting. README.md recommends:

To find the right IDs to use, issue the following command on the host, with the user owning the data volume on the host:

id

Which gives an output like this one:

uid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)

The value of uid (user ID) and gid (group ID) are the ones that you should be given the container.

In my case, I have a "BackupAgents" group and a "crashplan" user. All of the permissions are set by the group, not the user. Thus, for me:

id crashplan

Gives this:

uid=1234(crashplan) gid=100(users) groups=100(users),65536(BackupAgents)

Instead of using GROUP_ID=100 (which is the "users" group), I used GROUP_ID=65536 (the "BackupAgents" group).

The former caused no files to appear because users in the "users" group do not have permission, and the "crashplan" user also does not have explicit permission. But the "crashplan" user is a member of "BackupAgents" which DOES have permission.

Therefore, setting GROUP_ID to the proper group (the group that has permission) was important and solved my issue.

metastatic commented 6 years ago

@Tek4 Thanks for advice. I'll try this soon and will post the outcome later this week.

metastatic commented 6 years ago

@Tek4 Unfortunately no success.

Subsections of the output from docker inspect crashplan-pro command before the container is stopped after creation-:

        "Binds": [
            "/volumeUSB1/usbshare1-2:/volumeUSB1/usbshare1-2:rw",
            "/volume1/docker/appdata/crashplan-pro:/config:rw",
            "/volume1/:/volume1:ro"
        ],

   "Mounts": [
        {
            "Source": "/volume1",
            "Destination": "/volume1",
            "Mode": "ro",
            "RW": false,
            "Propagation": "rprivate"
        },

Subsections of the output from docker inspect crashplan-pro command after the container is restarted via the GUI-:

        "Binds": [
            "/volumeUSB1/usbshare1-2:/volumeUSB1/usbshare1-2:rw",
            "/volume1/docker/appdata/crashplan-pro:/config:rw"
        ],

No entries in the Mounts section match the entry above after the container was restarted.

@jlesage Can you recommend anything else I can try to resolve this issue?

metastatic commented 6 years ago

@jlesage What file are the environment variables written to?

Tek4 commented 6 years ago

@metastatic Here are my thoughts:

Full disclosure: I haven't yet restarted my setup, and won't until the initial backup completes. I may be in the same boat as you. We'll see...
It appears you have already ascertained a command line restart works. I'd like to see this proven over a couple reboots so we can safely rely on this.
If the above is reliable, can you show that a manual GUI start fails as opposed to an automatic start? Please ensure docker inspect has not already become tarnished by an auto start attempt before trying a manual GUI start. Even better, do a couple command line start/stop cycles prior to docker inspect and ensure the mounts succeed before attempting a manual GUI start. Try to definitively show a manual GUI start succeeds or fails, and let's be sure a reboot auto start isn't the sole culprit.
Next, I can't help but wonder if the USB volume is available early on during an automatic start. Perhaps an auto start fails because the USB volume isn't mounted yet? Perhaps a manualGUI start fails for a similar reason?
Can we remove the USB volume from your configuration and see if volume1 succeeds on its own? Maybe the USB failure causes everything subsequent to be dumped? Try reordering your configuration to place the USB volume last on the list.

When troubleshooting, I like to isolate potential issues and be able to rule-out confounding uncertainties. Start with a minimal configuration and check for success. Then add items one at a time. If a minimal configuration fails, it's time to delete everything and reinstall from ground zero. Create the most permissible permissions possible and use an admin user to attempt to establish a minimal successful configuration that you can build upon.

Cheers!

metastatic commented 6 years ago

@Tek4

No that's incorrect. I haven't ascertained that a command line restart works. I can create a new container ok, but I do not know how to restart the crashplan container from the command line.
Yes I can confirm that a manual GUI start fails as opposed to an automatic restart. Haven't tried a command line start/stop, as I haven't figured out how.
I can try without the USB. It's just a second backup destination

Thanks.

Tek4 commented 6 years ago

docker start jlesage/crashplan-pro

docker stop jlesage/crashplan-pro

Assuming the name of your container is the same.

Tek4 commented 6 years ago

Correction:

docker start crashplan-pro

Omit 'jlesage/' except for docker pull.

metastatic commented 6 years ago

@Tek4 Thanks. When I start the container via the command line the issue still occurs. I will now delete the container, clear the Crashplan config folder and then create the container using the following command

docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=4096M -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro

metastatic commented 6 years ago

@Tek4 I have found that after recreating the container I could stop and start it via the command line successfully. However, I then tried stopping and restarting via the GUI after which the issue reoccurred. Following that I attempted to restart via the command line, but the issue is still present.

The current DSM version installed is DSM 6.0.3-8754 Update 6

excalibr18 commented 6 years ago

@metastatic 1) Is the USB physically disconnected from the Synology? 2) Does the login you are using to log into DSM have admin rights?

metastatic commented 6 years ago

No. The office is 40 miles away
Yes. It is part of the administrators group. It has r/w access to all shares as confirmed in the Permissions tab for the user.

Tek4 commented 6 years ago

Absent a solution, I'm wondering if a work-around could be fashioned as a task to start the container via command line.

Since you've taken the USB binding out of the equation it's getting more interesting... I'd like to see the USB removed from the device at some point, but I don't expect that will make any difference.

Maybe try a differently named mounting point? Instead of "volume1" try "storage" or "foobar"?

Ensure you have the latest docker package and DSM version?

I'm just stabbing in the dark at this point.

Tek4 commented 6 years ago

I like to take a fresh look at all my syntax and spelling in these situations... For example, I notice your binding for config uses no trailing slash:

-v /volume1/docker/appdata/crashplan-pro:/config:rw

Compare with:

-v /volume1/:/volume1:ro

excalibr18 commented 6 years ago

@Tek4: Still worth looking into, however if the syntax was the culprit, wouldn't it prevent the container from working properly from the start? The thing though is that the container works as it should when initially created. It only breaks when the container is stopped and restarted from the Docker GUI or after a Synology reboot.

@metastatic: Can you post screen shots of the Container settings tabs from within the Docker GUI?

I'm also going to try attaching a USB hard drive to my Synology to see if I can replicate your issue tonight.

Tek4 commented 6 years ago

@excalibr18 Not necessarily. Clearly the GUI mechanism is processing things differently. Syntax might be relevant.

excalibr18 commented 6 years ago

@metastatic: Sorry metastatic, I cannot recreate your issue on my Synology. I'm running a Synology 1515+. DSM Version is DSM 6.1.5-15254. DSM date 2018/01/26. EDIT: Synology Docker Package version is 17.05.0-0367 Here's what I tried:

Deleted my existing container and image.
Downloaded the docker image from the Docker GUI interface.
SSH'd and created the container using: sudo docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=8192M -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1/:/volume1:ro jlesage/crashplan-pro
Attached an external USB drive and stopped and restarted the container from within the Docker GUI interface using the graphical 'switch'.
Confirmed volume1 mapping persists through the container restart. "Binds": [ "/volume1/docker/appdata/crashplan-pro:/config:rw", "/volume1/:/volume1:ro" ], { "Type": "bind", "Source": "/volume1", "Destination": "/volume1", "Mode": "ro", "RW": false, "Propagation": "" }, { "Type": "bind", "Source": "/volume1/docker/appdata/crashplan-pro", "Destination": "/config", "Mode": "rw", "RW": true, "Propagation": "" }
Stopped the container from within the Docker GUI.
Restarted the Synology with external USB attached.
Started the container from within the Docker GUI.
Reconfirmed volume1 mapping persists through the Synology restart.
Stopped the container from within the Docker GUI.
Deleted and recreated the container.
Confirmed volume1 mapping.
Restarted Synology with container still on.
Container did NOT restart automatically after reboot.
Started container from within the Docker GUI.
Confirmed volume1 mapping persists.

Tek4 commented 6 years ago

@excalibr18 You didn't indicate if you had the auto-start configuration enabled. Is there an issue with auto-start?

jlesage commented 6 years ago

One thing to consider is that Synology can, if I remember correctly, modify the config of a container instance without going through the usual steps of deleting and re-creating the container. For example, if you modify an environment variable, container won't be deleted and re-created.

So we can verify if the configuration changes at some point. In a normal Linux installation, container config is located at /var/lib/docker/containers/<container id>/config.v2.json. On Synology, this may be under /volume1/@docker, I'm not sure. The ID of a container can be retrieved via the docker inspect command. In the config, volume mappings are under MountPoints.

excalibr18 commented 6 years ago

@Tek4: I did not enable auto start. It is disabled by default on container creation (manually through command line).

excalibr18 commented 6 years ago

I can confirm the configuration file on the Synology is located in /volume1/@docker/containers/<container id>/config.v2.json

Tek4 commented 6 years ago

What if the config file was set to read-only?

@excalibr18 I would think auto start should be enabled.

bigtfromaz commented 6 years ago

@metastatic You can do everything you want with the Synology GUI. I have had good success with Synology and this package. If you want I can set up a Go2Meeting that you can join and I can walk you through the process and answer your questions. Others could join too if they are curious.

From: metastatic [mailto:notifications@github.com] Sent: Wednesday, February 7, 2018 3:27 PM To: jlesage/docker-crashplan-pro docker-crashplan-pro@noreply.github.com Cc: Tom Hebert (HCI) tom.hebert@hebert-consulting.com; Mention mention@noreply.github.com Subject: Re: [jlesage/docker-crashplan-pro] No files shown in folders mounted from NAS (#44)

No. The office is 40 miles away
Yes. It is part of the administrators group. It has access to all shares as confirmed in the Permissions tab for the user.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-crashplan-pro/issues/44#issuecomment-363932497, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHjxRuaHZCZn8GovKxCvAFffuMgQT_-eks5tSiNBgaJpZM4Ry9AV.

Tek4 commented 6 years ago

@bigtfromaz I'm interested. I am especially appreciative of the helpful post by @excalibr18 in #34.

excalibr18 commented 6 years ago

@bigtfromaz: I'd be interested in joining a Go2Meeting.

metastatic commented 6 years ago

Here's a screenshot of the container settings tabs from within the Docker GUI. Notice how the

USER_ID, GROUP_ID, CRASHPLAN_SRV_MAX_MEM and SECURE_CONNECTION variables are listed twice.

capture1

Here are the contents of the config.v2.json file before the container was restarted via the GUI-:

Here are the contents of the config.v2.json file after the container was restarted via the GUI-:

{"State":{"Running":true,"Paused":false,"Restarting":false,"OOMKilled":false,"RemovalInProgress":false,"Dead":false,"Pid":10680,"ExitCode":0,"Error":"","StartedAt":"2018-02-09T13:50:50.489619098Z","FinishedAt":"2018-02-09T13:50:12.79102729Z"},"ID":"750c0c78490d744dfa756442e9a0ae56924ec18c9a2c886c9707bc32e3f98e14","Created":"2018-02-09T13:17:57.044787134Z","Path":"/init","Args":[],"Config":{"Hostname":"750c0c78490d","Domainname":"","User":"","AttachStdin":false,"AttachStdout":false,"AttachStderr":false,"ExposedPorts":{"5800/tcp":{},"5900/tcp":{}},"Tty":false,"OpenStdin":false,"StdinOnce":false,"Env":["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","LANG=en_US.UTF-8","S6_BEHAVIOUR_IF_STAGE2_FAILS=3","S6_SERVICE_DEPS=1","USER_ID=0","GROUP_ID=0","APP_NAME=CrashPlan for Small Business","APP_USER=app","XDG_DATA_HOME=/config/xdg/data","XDG_CONFIG_HOME=/config/xdg/config","XDG_CACHE_HOME=/config/xdg/cache","DISPLAY=:0","DISPLAY_WIDTH=1280","DISPLAY_HEIGHT=768","S6_WAIT_FOR_SERVICE_MAXTIME=10000","KEEP_GUIAPP_RUNNING=1","CRASHPLAN_DIR=/usr/local/crashplan","JAVACOMMON=/usr/local/crashplan/jre/bin/java","CRASHPLAN_SRV_MAX_MEM=4096M","SECURE_CONNECTION=1"],"Cmd":["/init"],"Image":"jlesage/crashplan-pro","Volumes":{"/config":{},"/storage":{}},"WorkingDir":"/tmp","Entrypoint":null,"OnBuild":null,"Labels":{"org.label-schema.description":"Docker container for CrashPlan PRO","org.label-schema.name":"crashplan-pro","org.label-schema.schema-version":"1.0","org.label-schema.vcs-url":"https://github.com/jlesage/docker-crashplan-pro","org.label-schema.version":"2.1.1"},"DDSM":false},"Image":"sha256:7234b96df02a1ffa3c8e0f308fce108b791ed2d9e925dd316f1c117779795429","NetworkSettings":{"Bridge":"","SandboxID":"9dedabc89b0af21ecdebe67721f30b3514f187298f4076cb683826cb0f4eface","HairpinMode":false,"LinkLocalIPv6Address":"","LinkLocalIPv6PrefixLen":0,"Networks":{"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"e6bd44a6169efe54b96668c61df1b8ab418c59668af349b43b6b1a92a0b7f50e","EndpointID":"3fbe4bd611e2f4b455f607ddad19497a9148644f951ffa42798619c6c85bd12d","Gateway":"172.17.0.1","IPAddress":"172.17.0.2","IPPrefixLen":16,"IPv6Gateway":"fe80::1","GlobalIPv6Address":"fe80::242:ac11:2","GlobalIPv6PrefixLen":64,"MacAddress":"02:42:ac:11:00:02"}},"Ports":{"5800/tcp":[{"HostIp":"0.0.0.0","HostPort":"5800"}],"5900/tcp":null},"SandboxKey":"/var/run/docker/netns/9dedabc89b0a","SecondaryIPAddresses":null,"SecondaryIPv6Addresses":null,"IsAnonymousEndpoint":false},"LogPath":"/volume1/@docker/containers/750c0c78490d744dfa756442e9a0ae56924ec18c9a2c886c9707bc32e3f98e14/log.db","Name":"/crashplan-pro","Driver":"aufs","MountLabel":"","ProcessLabel":"","RestartCount":0,"HasBeenStartedBefore":false,"HasBeenManuallyStopped":false,"MountPoints":{"/config":{"Source":"/volume1/docker/appdata/crashplan-pro","Destination":"/config","RW":true,"Name":"","Driver":"","Relabel":"rw","Propagation":"rprivate","Named":false},"/storage":{"Source":"","Destination":"/storage","RW":true,"Name":"621ced80358ce23756de47c22227d82f9218a6ce895aa747c4c1d8cf8e322202","Driver":"local","Relabel":"","Propagation":"","Named":false},"/volumeUSB1/usbshare1-2":{"Source":"/volumeUSB1/usbshare1-2","Destination":"/volumeUSB1/usbshare1-2","RW":true,"Name":"","Driver":"","Relabel":"rw","Propagation":"rprivate","Named":false}},"AppArmorProfile":"","HostnamePath":"/volume1/@docker/containers/750c0c78490d744dfa756442e9a0ae56924ec18c9a2c886c9707bc32e3f98e14/hostname","HostsPath":"/volume1/@docker/containers/750c0c78490d744dfa756442e9a0ae56924ec18c9a2c886c9707bc32e3f98e14/hosts","ShmPath":"/volume1/@docker/containers/750c0c78490d744dfa756442e9a0ae56924ec18c9a2c886c9707bc32e3f98e14/shm","ResolvConfPath":"/volume1/@docker/containers/750c0c78490d744dfa756442e9a0ae56924ec18c9a2c886c9707bc32e3f98e14/resolv.conf","SeccompProfile":"","NoNewPrivileges":false}

metastatic commented 6 years ago

Here's a screenshot of the volumes. This was taken after the container was restarted via the GUI-:

capture2

metastatic commented 6 years ago

Latest version of DSM already installed.

capture3

jlesage commented 6 years ago

We see that after the restart, the mapping of /volume1 has been removed.

Since mapping of /volume1 seems problematic/not supported, why not mapping folders under it instead?

metastatic commented 6 years ago

@jlesage

I'm not entirely sure what you mean.

I tried the following with no success. The same issue occurred.

Created a symlink to volume1 called "volume1-symlink"
Created the container via the following command

sudo docker run -d --name=crashplan-pro -e USER_ID=0 -e GROUP_ID=0 -e CRASHPLAN_SRV_MAX_MEM=4096M -e SECURE_CONNECTION=1 -p 5800:5800 -v /volume1/docker/appdata/crashplan-pro:/config:rw -v /volume1-symlink/:/volume1-symlink/:ro -v /volumeUSB1/usbshare1-2/:/volumeUSB1/usbshare1-2/:rw jlesage/crashplan-pro

jlesage / docker-crashplan-pro

No files shown in folders mounted from NAS #44