Is there an existing issue for this?

• I have searched the existing issues

Does this issue exist in the latest version?

• I'm using the latest release

Describe the bug?

the arm_user_files_setup.sh script unnecessarily tries to chown directories, which will do nothing useful on most installs, and cause issues with anyone who has setup their nas to not allow random services to chown directories in the nas shares

if you have NFS setup to force specific groups so that every service you have is happy and does not encounter errors as random docker containers all have their own users/groups, these chown calls will fail causing the entire script to fail, causing the docker image to never enter a started state

To Reproduce

1. setup NFS with a mapall option to map all users to a specific user
2. try and launch the ARM docker container
3. observe failure

Built from source files ?

• I Built the image from source

What architecture are you seeing the problem on?

arm64

Expected behavior?

the script should not attempt to chown folders that are expected to be mounted, it's always going to end in failure as different systems have different UAC requirements, it should just live within the defined permissions of the folders that are mounted.

Relevant log output

*** Running /etc/my_init.d/arm_user_files_setup.sh...
Updating arm group id 1000 to default (1000)...
usermod: no changes
Updating arm group id from 1000 to 1003...
Adding arm user to 'render' group
chown: changing ownership of '/home/arm/media': Operation not permitted

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct