Replies: 1 comment
-
|
Hello thanks for reporting the issue, it is indeed very strange to see it from the container cli but not inside the app. I'll try to reproduce and find the problem |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I wanted to back up my files on my secondary partition (formatted as ext4). The partition is mounted at
/mnt/datawith write permissions for the owner and group. However, when I create a new volume in the Zerobyte UI, subfolders within the directory are not listed. This works correctly when I use a folder within my Home directory.This is my folder on the mounted partition, which is mapped to the Docker volume at

/mydata/mntIn my home directory, mapped to

/mydata/homedocker-compose:

When I created a new Zerobyte volume, the subfolders within

/mydata/mntwere not visible, even though they appeared correctly in/mydata/homeI thought it was a folder permission problem, but when I access the folder within the container, it shows up.

How can I solve this? Is there a setting in Zerobyte I'm missing for external mounts, since the files are visible via CLI but not in the UI, is this a known issue with how Zerobyte indexes external partitions? Any help or insights would be greatly appreciated. Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions