#is UID/GID 1000 hard coded?
20 messages · Page 1 of 1 (latest)
Nope, the container is rootless and uses node's user - which has 1000 as UID and GID
Im a bit lost on this cause on Truenas UID/GID 1000 doesnt exist. Yes we can use the chown command and it will give the non-existent user acces and it will work, but that then removes my ability to do anything in the dataset/folder.. whats the solution for truenas to have seerr work without breaking user permissions?
You might want to look into acls
Yeah I did, but truenas wont let me set it for 1000 since user dont exist
You can just pass in user: x:x
And run as any user you want too
Not possible in the truenas webui but yeah is via shell.
In webui as soon as you click off the field goes empty
What
Im talking about docker container
You can pass in a user
Uh, I read that Seerr was hardcoded to use 1000:1000 even if you changed it
Is this wrong?
https://wiki.serversatho.me/en/seerr#h-2-permissions-docker-only
https://docs.seerr.dev/getting-started/docker mentions it runs as the 1000 node user though nothing about it being hardcoded and not being able to be changed in that link
You can use user: xx:xx
Thats explained in the unraid setup too in our official docs. Idk what serversatho.me is
Its recommended to use 1000:1000
But you can use user: xx:xx
I created a new user in Truenas under Credentials called "node" with a USER ID:1000, and then under the ACLS, i put NODE in it