Unable to select local folders to backup.
cloudymark opened this issue · 14 comments
How did you created the container?
Could you also provide the output of the following commands:
docker inspect [container name]
docker exec [container name] df -h
docker exec [container name] ls -l /
Sorry your attachment is missing. You need to attach files using the github web interface.
Apologies.
df.txt
inspect.txt
ls.txt
My guess is that the software doesn't display the folder because of its filesystem:
mergerfsPool 4.5T 1012.3G 3.3T 23% /storage
I will try to contact CloudBerry team to see if this can be fixed.
Well that was my assumption, but when I added a link in the config folder to storage, i am able to browse to it fine and then select it for backup.
Also, why do I not see the local files system within the docker image? Or is that by design?
Well that was my assumption, but when I added a link in the config folder to storage, i am able to browse to it fine and then select it for backup.
Yes so it's in fact just a UI bug. The /storage
folder is not shown even if it exists and accessible.
Also, why do I not see the local files system within the docker image? Or is that by design?
What do you mean exactly be the "local files system" ?
The file system in the docker image itself. It doesn't even show those folders. It just targets the config folder and some other random files.
I think it's because of the same issue: the root /
is mounted with an overlay
filesystem, something probable not recognized by the UI.
Any update on this issue? I have the same problem. My /storage docker volume is mapped to a ZFS pool on the host. When I start this docker image, I can see /storage and browse it and see all my files within the ZFS pool. However when trying to setup a backup, this storage folder does not exist in the UI. Even if I place a symbolic link in the config folder to /storage, it still doesn't show up. Any ideas?
Unfortunately I didn't get answers yet from CloudBerry about this issue. I pinged them again yesterday.
To document unsupported filesystems, can you post the output of docker exec [container name] df -h
?
Having the same issue as well all of a sudden. The GUI was still working two weeks ago, then after a reboot of the host I'm not seeing the paths anymore. However, since the configuration is still in tact, I can still perform backups using the same backup plan. Unable to make any changes to it though.
Looks like an issue where the mounts on the host were not ready at the time the container was started. Did you try to restart the container again to see if you still get the issue ?
Looks like an issue where the mounts on the host were not ready at the time the container was started. Did you try to restart the container again to see if you still get the issue ?
I have tried restarting and still get the issue.