jesta Posted January 26, 2022 Share Posted January 26, 2022 I set up FileRun using @BamaJ13's docker template and ran into the issue that files created/uploaded through FileRun's webUI are readonly to other users and thus can't be modified over for example SMB. I first tried very long to launch the docker with different user:group settings and messing with ACLs but couldn't get it to work. Then I dug long and deep and found an undocumented solution. Here are the two steps needed: add two environment variables in template: "APACHE_RUN_GROUP = users" and "APACHE_RUN_GROUP_ID = 100" after first run, modify or create file /mnt/user/appdata/filerun/customizable/config.php with following content: <?php umask(012); Then all files/dirs created by FileRun will belong to group "users" and have read and write access for other users of UnRAID. Have fun! 1 Quote Link to comment
chronkus Posted February 5, 2022 Share Posted February 5, 2022 I had some similar issues: In addition to step 1 from above, I also had to empty the "system/data/temp/smarty" folder Quote Link to comment
insomnia417 Posted June 14, 2022 Share Posted June 14, 2022 谢谢楼主,找了整整一天,最后在这里解决了问题,如果不输入userid. 那么默认就会是1000权限,然后我修改umask为0112就解决了 但是还有个问题就是我希望让/user-files/这个文件默认创建就是mobody不知道怎么弄, filerun是个好软件,但是跟nextcloud一样权限问题太让人头大了!! Quote Link to comment
acidburn666 Posted January 21, 2023 Share Posted January 21, 2023 On 1/26/2022 at 10:52 PM, jesta said: I set up FileRun using @BamaJ13's docker template and ran into the issue that files created/uploaded through FileRun's webUI are readonly to other users and thus can't be modified over for example SMB. I first tried very long to launch the docker with different user:group settings and messing with ACLs but couldn't get it to work. Then I dug long and deep and found an undocumented solution. Here are the two steps needed: add two environment variables in template: "APACHE_RUN_GROUP = users" and "APACHE_RUN_GROUP_ID = 100" after first run, modify or create file /mnt/user/appdata/filerun/customizable/config.php with following content: <?php umask(012); Then all files/dirs created by FileRun will belong to group "users" and have read and write access for other users of UnRAID. Have fun! Thanks for the description. I ran into the exact same issue. Can you please add a screenshot of the variables? I don´t get it correctly, what to add wihtin the variable fields. Best regards! Quote Link to comment
DebrodeD Posted August 29 Share Posted August 29 (edited) Adding those variables into the template and the umask into the config file hasn't worked for me. New folders created from within Filerun are still listed as "UNKNOWN" under owner in Unraid and are read-only on SMB. Anything I'm missing? Edited August 29 by DebrodeD Quote Link to comment
DebrodeD Posted August 30 Share Posted August 30 I can fix the permissions issue by setting the umask to 000, but that doesn't fix the owner issue. Quote Link to comment
DebrodeD Posted August 30 Share Posted August 30 Fixed the owner issue, the above advice no longer works with the recent update (at least for me), you need to create 4 new variables and set them to these values: Name: Apache Run User Key: APACHE_RUN_USER Value: 99 Name: Apache Run User ID Key: APACHE_RUN_USER_ID Value: 99 Name: Apache Run Group Key: APACHE_RUN_GROUP Value: 100 Name: Apache Run Group ID Key: APACHE_RUN_GROUP_ID Value: 100 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.