You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using bind mounts in a docker container running with the current image will result in the docker user assuming ownership of the bound directories and its files, leading to permission problems for the result files.
To Reproduce
Run faunanet in docker and feed it some data with a directory in the user's home directory being mounted, then see how the the user does not have write permission on the files
Expected behavior
Permissions for output data should be granted to the user as if in a native run.
machine/OS
Linux. On macOS, this is automatically taken care of.
The text was updated successfully, but these errors were encountered:
There's no good fix for this I could make work. Either you have to build a new docker container for every user or run the whole thing in docker desktop, neither of which is useful by any stretch for remote edge devices.
Describe the bug
Using bind mounts in a docker container running with the current image will result in the docker user assuming ownership of the bound directories and its files, leading to permission problems for the result files.
To Reproduce
Run faunanet in docker and feed it some data with a directory in the user's home directory being mounted, then see how the the user does not have write permission on the files
Expected behavior
Permissions for output data should be granted to the user as if in a native run.
machine/OS
Linux. On macOS, this is automatically taken care of.
The text was updated successfully, but these errors were encountered: