Unable to get D: drive working on Unraid #66
Comments
|
Permissions. Make sure the directory /mnt/user and symlink /wine/dosdevices/d: are owned by app:app, not root.
… On Aug 26, 2023, at 6:45 PM, rbisker ***@***.***> wrote:
I'm running the docker on Unraid and after install executed the command
docker exec --user app Backblaze_Personal_Backup ln -s /mnt/user /config /wine/dosdevices/d:
From the unraid shell I see a syslink "d:" in /mnt/user/appdata/Backblaze_Personal_Backup/wine/dosdevices, and when I browse with the ls command I see all of my shares listed.
However, when I start the docker, D: is not available as option in Backblaze. Also, when I run sudo docker exec --user app backblaze-backup-backblaze-1 wine explorer, I see a D: drive listed, but it is empty.
<https://user-images.githubusercontent.com/31449097/263503891-c2717eb4-5159-4e48-a7a8-bc36ee2b4720.png>
Any idea what I'm doing wrong here? Does this not work if you're making a symbolic link to Unraid share folders as opposed to directories on specific disks?
—
Reply to this email directly, view it on GitHub <#66>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACLQM6CIL37V6XAPP4GUV2TXXKRE7ANCNFSM6AAAAAA3764K3E>.
You are receiving this because you are subscribed to this thread.
|
|
Sorry I'm a Linux/Docker novice. When you say change the user:group to app:app, do I literally type 'chown app:app' or is 'app' supposed to be the group ID of something in the docker, and if so how do I figure out what that is?
|
|
Yes. Exec into the container with docker exec -it and literally chows them
with app:app. The wine process is owned and run by the “app” user.
…On Sat, Aug 26, 2023 at 10:06 PM rbisker ***@***.***> wrote:
Sorry I'm a Linux/Docker novice. When you say change the user:group to
app:app, do I literally type 'chown app:app' or is 'app' supposed to be the
group ID of something in the docker, and if so how do I figure out what
that is?
Permissions. Make sure the directory /mnt/user and symlink
/wine/dosdevices/d: are owned by app:app, not root.
—
Reply to this email directly, view it on GitHub
<#66 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACLQM6CHMW6UL47LU3DT2VTXXLIT5ANCNFSM6AAAAAA3764K3E>
.
You are receiving this because you commented.Message ID:
<JonathanTreffler/backblaze-personal-wine-container/issues/66/1694571445@
github.com>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running the docker on Unraid and after install executed the command
docker exec --user app Backblaze_Personal_Backup ln -s /mnt/user /config /wine/dosdevices/d:From the unraid shell I see a syslink "d:" in /mnt/user/appdata/Backblaze_Personal_Backup/wine/dosdevices, and when I browse with the ls command I see all of my shares listed.
However, when I start the docker, D: is not available as option in Backblaze. Also, when I run
sudo docker exec --user app backblaze-backup-backblaze-1 wine explorer, I see a D: drive listed, but it is empty.Any idea what I'm doing wrong here? Does this not work if you're making a symbolic link to Unraid share folders as opposed to directories on specific disks?
The text was updated successfully, but these errors were encountered: