Unraid migration documentation

[zer0ish]

Description

This isn't a bug, but something that should be added to the documentation for Unraid section.

This is for users going from Jellyseerr to Seerr and wanting to maintain their setup.
I havent tested with Overseerr since I didn't use that one.

Unraid uses user "nobody" "99:100" for docker containers.
To use this user, you must add "--user 99:100" to the Extra Parameters section under the advanced toggle.
If you don't, the container will fail to start.

I didn't lose anything during the migration from Jellyseerr to Seerr.

Version

3.0.1

Steps to Reproduce

Follow the guide provided by the Seerr team.
Add "--user 99:100" to the Extra Parameters section under the advanced toggle.

Screenshots

No response

Logs

Platform

desktop

Database

SQLite (default)

Device

browser

Operating System

Unraid

Browser

Brave

Additional Context

No response

Search Existing Issues

• Yes, I have searched existing issues.

Code of Conduct

• I agree to follow Seerr's Code of Conduct

[M0NsTeRRR]

hello @mjonkus can you confirm the issue and could you fix the guide if it's the case ?

[zer0ish]

I should probably clarify that I didn't do step 3 because I wanted to use the default docker user for unraid (nobody).
I changed the ownership of all folders to nobody and when I start the container without the --user 99:100 extra parameter it doesn't start because of permission issues. But when adding the --user 99:100 extra parameter and all folders are set to be owned by nobody user, Everything works great.

[mjonkus]

The current guide assumes the user adopts Seerr's default node user (UID 1000) and chowns the appdata accordingly. @zer0ish's approach is good as well by keeping Unraid's default nobody:users (99:100) ownership and passing --user 99:100 to the container instead.

That said, I'm not fully familiar with how Next.js handles this internally. The Seerr image is built and tested against UID 1000, so overriding with --user 99:100 could potentially cause issues if future updates introduce internal paths that expect the node user. It works today, but could lead to a breaking change later.

From a simplicity perspective it makes sense though. Keeping all Unraid containers under the same UID is a common pattern. And since users already need to add --init to Extra Parameters, adding --user 99:100 would be a straightforward addition.

@M0NsTeRRR I can submit a PR to document this as an alternative approach with an appropriate disclaimer. Would that work or is better to keep as is?

[M0NsTeRRR]

I should probably clarify that I didn't do step 3 because I wanted to use the default docker user for unraid (nobody).

Yes, because it's not an issue, you just use a different setup.

@mjonkus Yes, you can. It seems Unraid doesn’t follow standard Linux practices, so I’m not sure how it works. Since Unraid uses a non-standard setup, we can’t prevent breaking changes.

[milapointe]

i am having the same issue.

I added

-e 'PUID'='99'
-e 'PGID'='100'
-e 'UMASK'='022'

but still, the template doesnt take them from variable.

Had to do what you did, --init --user 99:100.

The permanent fix would be the template being able to use the variables.

[aterriblegamer]

Yes please add support for me passing in the PUID and PGID of the user I want to run the container in my environment. I dont want to alter my permissions for one app.

[fallenbagel]

Yes please add support for me passing in the PUID and PGID of the user I want to run the container in my environment. I dont want to alter my permissions for one app.

#2455 (comment)

However you can follow these instructions
#2470 (will be added to docs once merged)

[thunderclap82]

Just wanted to thank @zer0ish. I couldn't figure out why Seerr wasn't starting on a fresh install. This fixed it for me.

[milapointe]

Just wanted to thank @zer0ish. I couldn't figure out why Seerr wasn't starting on a fresh install. This fixed it for me.

Me too, solved my problem and it followed unraid best practice. Thanks.

I opened up a change for the unraid template here : nwithan8/unraid_templates#435