akhisyahmi Posted October 18, 2023 Share Posted October 18, 2023 I keep getting these problem whenever I download from qbittorrent. The only fix i know is to run new perm but its only for short term and iwill need to run it again when new files downloaded. Any idea how to set qbit to allow move/copy/modify files it download? Thanks. Quote Link to comment
Solution Frank1940 Posted October 18, 2023 Solution Share Posted October 18, 2023 You need to go to the 'qbit' Docker, left click on its icon, select 'Edit', and look for the keys with 'PARADYNE' and 'nobody' as the editable variables. Change them to 'nobody' and 'users'. If this does not work, go to the support thread for this Docker and ask there. Quote Link to comment
akhisyahmi Posted October 19, 2023 Author Share Posted October 19, 2023 22 hours ago, Frank1940 said: If this does not work, go to the support thread for this Docker and ask there. Hi, sorry for the late response. I will try it later. Thank you. Quote Link to comment
akhisyahmi Posted October 19, 2023 Author Share Posted October 19, 2023 On 10/18/2023 at 7:10 PM, Frank1940 said: If this does not work, go to the support thread for this Docker and ask there. Nothing here Quote Link to comment
Frank1940 Posted October 19, 2023 Share Posted October 19, 2023 (edited) Go here to find support thread: Edited October 20, 2023 by Frank1940 Quote Link to comment
akhisyahmi Posted October 23, 2023 Author Share Posted October 23, 2023 I edit all my docker qbit, sonarr, radarr and etc to UMASK 000 and now that seems to fix it. Quote Link to comment
crazycajun Posted July 21 Share Posted July 21 (edited) On 10/23/2023 at 8:44 AM, akhisyahmi said: I edit all my docker qbit, sonarr, radarr and etc to UMASK 000 and now that seems to fix it. do you have a picture of where this is? i dont have umask in my docker settings. Edited July 21 by crazycajun Quote Link to comment
Frank1940 Posted July 21 Share Posted July 21 (edited) While in the Edit option of the Docker dropdown, make sure that you have clicked on the 'Show more settings' dropdown. If it not there, go to the support link for that Docker and ask this question there. NOTE: Setting the UMASK variable is not required unless that directories created in the User Shares by that Docker container are not 777. (Files should be 666. It could be 777 but that setting is not recommended for strictly data files.) This does not apply to any files in the appdata share. That share is intended to accessed by only Docker containers to store their files in. A Share Access user should ever have to access appdata share for data! The owner, group and permissions are set to permit the Docker container to access files for its own use. Edited July 21 by Frank1940 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.