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
I am using unraid (i know :)...) and while I am trying to install this on my unraid, I see that only wants to use root:root as owner permissions, unlike unraid that always uses nobody:users.
Is there something wrong there? I have tried to use on docker compose UMASK=002 as well, but it's the same thing.
For now, I have chowned my roms folder ONLY to nobody:users and I can add roms I download manually this way.
Thanks for making such an amazing tool!! :)
The text was updated successfully, but these errors were encountered:
piratx
changed the title
root:root permissions only in the created folders?
On unraid install root:root permissions only in the created folders?
Sep 21, 2024
piratx
changed the title
On unraid install root:root permissions only in the created folders?
On unraid install root:root owner only in the created folders?
Sep 21, 2024
@piratx jaybird2203 is right, you can control the user running the app within the container with the PUID and GUID environment variables in the docker-compose, it has to match whatever returns the id command executed by the "nobody" user.
Hello,
I am using unraid (i know :)...) and while I am trying to install this on my unraid, I see that only wants to use root:root as owner permissions, unlike unraid that always uses nobody:users.
Is there something wrong there? I have tried to use on docker compose UMASK=002 as well, but it's the same thing.
For now, I have chowned my roms folder ONLY to nobody:users and I can add roms I download manually this way.
Thanks for making such an amazing tool!! :)
The text was updated successfully, but these errors were encountered: