From 5e64d49c32a8510d1f19b62395e46b78476084a3 Mon Sep 17 00:00:00 2001 From: blassley <49504228+blassley@users.noreply.github.com> Date: Mon, 16 Feb 2026 18:12:47 -0600 Subject: [PATCH] docs(unraid): improve unraid migration guide (#2470) --- docs/getting-started/third-parties/unraid.mdx | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/getting-started/third-parties/unraid.mdx b/docs/getting-started/third-parties/unraid.mdx index 4d43f419..bb53b9b7 100644 --- a/docs/getting-started/third-parties/unraid.mdx +++ b/docs/getting-started/third-parties/unraid.mdx @@ -21,6 +21,14 @@ If an official Unraid Community Applications template for Seerr isn't available ### 1. Create the config directory +:::note +Seerr is now rootless. Unraid typically runs Docker containers as `nobody:users` (UID 99, GID 100), but Seerr now runs internally as UID 1000, GID 1000. This creates a permission mismatch. +::: + +:::info +**If migrating**: Copy your existing Jellyseerr/Overseerr config files (e.g., from `/mnt/user/appdata/overseerr/` or `/mnt/user/appdata/jellyseerr`) to `/mnt/user/appdata/seerr`, then apply the permissions below +::: + Open the Unraid terminal and run: ```bash @@ -78,4 +86,4 @@ Open the WebUI at `http://:5055` and follow the setup wizard. :::info The `--init` flag in **Extra Parameters** is required. Seerr does not include its own init process, so `--init` ensures proper signal handling and clean container shutdowns. -::: \ No newline at end of file +:::