docs: Updates the Unraid documentation for alternative way to deploy Seerr using correct file system permissions and prevent access issues

docs/getting-started/third-parties/unraid.mdx

@@ -11,11 +11,13 @@ Third-party installation methods are maintained by the community. The Seerr team
 :::
 
 :::warning
-This method is not recommended for most users. It is intended for advanced users who are using Unraid.
+This manual method is not recommended for most users. It is intended for advanced users who are using Unraid.
 :::
 
+Several templates from Unraid Community are available right now
+- [Unraid Community Apps](https://unraid.net/community/apps#community-apps-iframe)
 
-If an official Unraid Community Applications template for Seerr isn't available in your catalog, you can install Seerr manually using Unraid's Docker UI.
+In case you still want to do it manually, please follow the instructions below.
 
 ## Fresh Installation
 
@@ -33,23 +35,41 @@ Open the Unraid terminal and run:
 
 ```bash
 mkdir -p /mnt/user/appdata/seerr
-chown -R 1000:1000 /mnt/user/appdata/seerr
 ```
 
+You have two options to avoid permission issues caused by Unraid running containers as `nobody:users` (UID 99, GID 100) while Seerr runs internally as UID 1000, GID 1000:
+
+- Recommended: change ownership of the config folder on the host so Seerr runs with its native UID/GID:
+
+  ```bash
+  chown -R 1000:1000 /mnt/user/appdata/seerr
+  ```
+
+- Alternative:
+
+  ```bash
+  chown -R 99:100 /mnt/user/appdata/seerr
+  ```
+
+  Explaination : Do not change host ownership and instead run the container as Unraid's `nobody:users` by adding the extra Docker parameter `--user 99:100` when creating the container. This runs the container process with Unraid's default UID/GID and avoids permission errors accessing your shares.
+
+:::warning
+Do not use both approaches at the same time, either change the host folder ownership to `1000:1000` or run the container with `--user 99:100`. Mixing both can create confusing ownership and permission states.
+:::
 ### 2. Add the Docker container
 
 Navigate to the **Docker** tab in Unraid and click **Add Container**. Fill in the following:
 
-| Field | Value |
-|---|---|
-| **Name** | `seerr` |
-| **Repository** | `ghcr.io/seerr-team/seerr:latest` |
-| **Registry URL** (optional) | `https://ghcr.io` |
-| **Icon URL** | `https://raw.githubusercontent.com/seerr-team/seerr/develop/public/android-chrome-512x512.png` |
-| **WebUI** | `http://[IP]:[PORT:5055]` |
-| **Extra Parameters** | `--init` |
-| **Network Type** | `bridge` |
-| **Privileged** | `Off` |
+| Field | Value | Note |
+|---|---|---|
+| **Name** | `seerr` ||
+| **Repository** | `ghcr.io/seerr-team/seerr:latest` ||
+| **Registry URL** (optional) | `https://ghcr.io` ||
+| **Icon URL** | `https://raw.githubusercontent.com/seerr-team/seerr/develop/public/android-chrome-512x512.png` ||
+| **WebUI** | `http://[IP]:[PORT:5055]` ||
+| **Extra Parameters** | `--init` | `--init --user 99:100` for the alternative approach |
+| **Network Type** | `bridge` ||
+| **Privileged** | `Off` ||
 
 Then click **Add another Path, Port, Variable** to add:
 

docs/migration-guide.mdx

@@ -229,6 +229,10 @@ cp -a /mnt/user/appdata/overseerr /mnt/user/appdata/overseerr-backup
 ```bash
 chown -R 1000:1000 /mnt/user/appdata/overseerr
 ```
+:::info
+**If migrating**: See [Seerr Unraid Documentation](/getting-started/third-parties/unraid) for alternative method for permissions if you prefer not to change host folder ownership.
+:::
+
 For Jellyseerr users, replace `overseerr` with `jellyseerr` in the path above.
 
 4. Add a new container in the Unraid **Docker** tab. Click **Add Container** and fill in the following:
@@ -277,4 +281,4 @@ For Jellyseerr users, use `/mnt/user/appdata/jellyseerr`.
 
 :::tip
 If you are using a reverse proxy (such as SWAG or Nginx Proxy Manager), update your proxy configuration to point to the new container name `seerr`. The default port remains `5055`.
-:::
+:::