elmuziko Posted May 12 Share Posted May 12 Evening, Following instructions for Redis docker but because I'm daft, I think I've done some damage to Unraid and could do with some help. Assume I'm going to need to run chown -R root / to resolve this? Or more to it than that? Quote Link to comment
bmartino1 Posted May 12 Share Posted May 12 it is for this reason that unraid made this tool: /Tools/DockerSafeNewPerms by default, unraid has docker in the appdata folder. This will reapply the correct docker safe permissions per unraid. Unraid claism this to be correct: For directories: drwxrwxrwx For read/write files: -rw-rw-rw- For read-only files: -r--r--r-- Otherwise, I recommend a open reset of permission until the docker touches the file. as i have seen docker is puid / uuid / guid settings have file permission of user 999 etc which are out of scope in unraid but correct per the docker permission set. Redis may require a more secure file type 640 is the normal default secure for user only access. cd /mnt/appdata/ chmod -R 777 * chown nobody:users -R * ^This will reapply so that every user can write edit detle touch etc. Quote Link to comment
elmuziko Posted May 13 Author Share Posted May 13 Hiya, Thanks for the response. Having ran it, it's worked against everything in /mnt but not the higher leveled stuff from the image. It doesn't seem to have changed the permissions, only owner. 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.