Change PUID on container after the install - Permission issues?

Sorion · 9. Mai 2023

Hey guys,

so I got a uncertainty I want to kinda run by folks that have a better understanding than I do.

I setup my docker plugin in accordance with your frequently linked tutorial, created my user, changed directory and etc.

But lack of attention I created the jellyfin container in portainer under the standart config which set the user to GUID 1024 instead of the appuser I created of 1002.

Obviously I could just ditch what I have and recreate the container, but it's been a few days and I only now noticed and would like to not reconfigure jellyfin so I'd rather change stuff.

So here's my question:

I found the option in the container to change the GUID, but I did not beforeend create the jellyfin/config folder so that one was generated with the 1024 user, so I'd expect me simply changing it will run into permission issues later on.

Am I correct about this?

If yes, how would I change the owner or add proper permissions to the appuser to modify that folder and not run into that?

Maybe the GUID 1002 being part of the group "docker" (which I did not create but apparently got automatically setup by the docker installation process?) already makes this a non issue? Not sure.

Greetings

chente · 9. Mai 2023

Zitat von Sorion

I found the option in the container to change the GUID, but I did not beforeend create the jellyfin/config folder so that one was generated with the 1024 user, so I'd expect me simply changing it will run into permission issues later on.
Am I correct about this?
If yes, how would I change the owner or add proper permissions to the appuser to modify that folder and not run into that?

Maybe the GUID 1002 being part of the group "docker" (which I did not create but apparently got automatically setup by the docker installation process?) already makes this a non issue? Not sure.

Did you follow this procedure? https://wiki.omv-extras.org/do…ing_and_installing_docker

If you followed it the /SSD/appdata/jellyfin folder should have 775 permissions and the owner group should be users

If the user assigned to manage the container belongs to the users group, there should be no problem.

show the output of

ls -al /SSD/appdata/jellyfin

Sorion · 9. Mai 2023

Zitat von chente

Did you follow this procedure? https://wiki.omv-extras.org/do…ing_and_installing_docker
If you followed it the /SSD/appdata/jellyfin folder should have 775 permissions and the owner group should be users
If the user assigned to manage the container belongs to the users group, there should be no problem.
show the output of
ls -al /SSD/appdata/jellyfin

Code

$ ls -al /SSD/docker/jellyfin
total 12
drwxr-xr-x  3 root root  4096 May  6 10:34 .
drwx--s--- 13 root users 4096 May  9 12:34 ..
drwxr-xr-x  7 1024 users 4096 May  6 11:29 config

Thema

[How to] Docker in OMV

______________________________________________________________________________________________________________
______________________________________________________________________________________________________________

THIS GUIDE HAS BEEN MOVED TO THE OMV-EXTRAS WIKI.
FOLLOW THIS LINK -> https://wiki.omv-extras.org/doku.php?id=omv7:docker_in_omv
______________________________________________________________________________________________________________

…

chente

16. Oktober 2021

This is what I mostly followed, and linking it I noticed the big red info on top - my lack of attention has already been stated :s

Maybe I'll actually redo with the wiki, just to be sure.

chente · 9. Mai 2023

Zitat von Sorion

This is what I mostly followed, and linking it I noticed the big red info on top - my lack of attention has already been stated :s

Maybe I'll actually redo with the wiki, just to be sure.

It's the same guide, don't worry about it. Just last weekend I moved it to the wiki. Now it is prettier but the procedure remains the same

Zitat von Sorion

drwxr-xr-x 7 1024 users 4096 May 6 11:29 config

As you can see, the owning group is users. So just make sure that your user belongs to this group. If you haven't modified it, all users created in the OMV GUI belong to the users group.

You could modify the owner of the folder, at the moment it is user 1024, but I don't know if this would affect Jellyfin. I would say no, but I'm not sure. I wouldn't touch anything.

chente · 9. Mai 2023

Zitat von Sorion

drwxr-xr-x 7 1024 users 4096 May 6 11:29 config

Sorry, I hadn't noticed this.

This is a problem, the folder does not have 775 permissions, the users group cannot write. You must modify that.

drwxr-xr-x -> group permissions are r-x, w is missing

chente · 9. Mai 2023

I would do the following.

First make a backup of that folder.

Then install resetperms https://wiki.omv-extras.org/do…6:omv6_plugins:resetperms

Reset the permissions of that folder to the default permissions 775 owner root and group owner users.

Try it, if it works correctly, delete the backup. If it doesn't work come back here.

Sorion · 9. Mai 2023

Zitat von chente

I would do the following.
First make a backup of that folder.
Then install resetperms https://wiki.omv-extras.org/do…6:omv6_plugins:resetperms
Reset the permissions of that folder to the default permissions 775 owner root and group owner users.
Try it, if it works correctly, delete the backup. If it doesn't work come back here.

Code

$ ls -al /SSD/docker/jellyfin
total 12
drwxrwsr-x  3 root users 4096 May  6 10:34 .
drwxrwsr-x 13 root users 4096 May  9 12:34 ..
drwxrwsr-x  7 root users 4096 May  6 11:29 config

I feel like this made it worse? Not entirely sure if x is now everything or just .. nothing?

Also, apparently my jellyfin folder is in the wrong subfolder too - should be in appdata according to the guide, so thats the second thing I botched.

chente · 9. Mai 2023

Zitat von Sorion

I feel like this made it worse? Not entirely sure if x is now everything or just .. nothing?
Also, apparently my jellyfin folder is in the wrong subfolder too - should be in appdata according to the guide, so thats the second thing I botched.

MMM....

let's go in parts...

The permissions of that folder are now correct, the users group has read and write permission.

Here you should find the meaning of those letters. https://wiki.omv-extras.org/do…misc_docs:nas_permissions

But...

Is the jellyfin folder installed in the same folder as docker? I hope not. There doesn't seem to be anything else in your docker folder besides the jellyfin folder.

Is it working now?

You have it a bit messy but it should be working. Maybe if you start from scratch you will avoid problems or misunderstandings later.

Sorion · 9. Mai 2023

So I decided to redo it, last time I did do it via portainer, so that might've caused issues too? But nevermind, I removed everything involving the old docker setup, including shared folders and folders itself and set everything back up.

So, fresh start stuck to the wiki and now I am getting this error once I check the file:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose//jellyfin/jellyfin.env' config 2>&1': parsing /srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose/jellyfin/jellyfin.yml: yaml: line 8: mapping values are not allowed in this context

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose//jellyfin/jellyfin.env' config 2>&1': parsing /srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose/jellyfin/jellyfin.yml: yaml: line 8: mapping values are not allowed in this context in /usr/share/openmediavault/engined/rpc/compose.inc:330
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatusJT...', '/tmp/bgoutputQO...')
#1 /usr/share/openmediavault/engined/rpc/compose.inc(333): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)
#6 {main}

Alles anzeigen

I'd like to note, that I always get an error during docker installation. But this one is not sent to the notifications tab and vanishes from screen after like 2 seconds so I never was able to read it.

But once reload Docker says to be installed and running so I didn't mind to much.

chente · 9. Mai 2023

Zitat von Sorion

So, fresh start stuck to the wiki and now I am getting this error once I check the file:

Please post your yml file. Skips personal values if any exist.

Zitat von Sorion

I'd like to note, that I always get an error during docker installation. But this one is not sent to the notifications tab and vanishes from screen after like 2 seconds so I never was able to read it.
But once reload Docker says to be installed and running so I didn't mind to much.

What kind of mistake? There should be no errors. Search the logs, maybe you'll find something.

Sorion · 9. Mai 2023

This is what you're refering to, right?

Code

$ cat /SSD/compose/jellyfin/jellyfin.yml
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.

# jellyfin
# media player

  ---
  version: "2.1"
  services:
    jellyfin:
      image: lscr.io/linuxserver/jellyfin:latest
      container_name: jellyfin
      environment:
        - PUID=1002
        - PGID=100
        - TZ=Europe/Berlin
      volumes:
        - /SSD/appdata/jellyfin:/config
        - /MEDIA/entertainment:/entertainment
      ports:
        - 8888:8096
      restart: unless-stopped
$

Alles anzeigen

As for the logs. Can you point me in a direction to look at? Because I wouldn't know where to find those.

chente · 9. Mai 2023

Zitat von Sorion

This is what you're refering to, right?

Is your user id really 1002?

post the output of

id YOUR_USER_NAME

Where YOUR_USER_NAME is the username that manages the container, appuser if you did so.

Zitat von Sorion

As for the logs. Can you point me in a direction to look at? Because I wouldn't know where to find those.

In the GUI under Diagnostics>System Logs>Logs Select Syslog. Download it and look for around the time you installed docker.

Sorion · 9. Mai 2023

Zitat von chente

Is your user id really 1002?
post the output of
id YOUR_USER_NAME
Where YOUR_USER_NAME is the username that manages the container, appuser if you did so.
In the GUI under Diagnostics>System Logs>Logs Select Syslog. Download it and look for around the time you installed docker.

Yeah that one was obvious should've stated it from the start.

Yes, my user is 1002 - I did not just copy it from the wiki:

Code

$ id appuser
uid=1002(appuser) gid=100(users) groups=100(users),992(docker)

Found the log will see if I can find it.

chente · 9. Mai 2023

and the output of

ls -al /SSD/appdata

Sorion · 9. Mai 2023

Zitat von chente

and the output of
ls -al /SSD/appdata

Code

$ ls -al /SSD/appdata
total 8
drwxrwsr-x 2 root users 4096 May  9 15:09 .
drwxr-xr-x 8 root root  4096 May  9 15:10 ..

chente · 9. Mai 2023

sorry

ls -al /SSD

Sorion · 9. Mai 2023

Zitat von chente

sorry
ls -al /SSD

Code

$ ls -al /SSD
lrwxrwxrwx 1 root root 58 May  6 10:05 /SSD -> /srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec

No worries, thankful to recieve help here

Also, I still have difficulties reading that line - but there should be a users in there, right?

So my rights are wrong? - that would be an issue from, before my reset - the SSD dir has not been touched in this last setup

If that's the case I'll go with follow up question immediately.

I cant select the SSD path in reset permissions.

Can I just create one and then select it to reset? Does that work?

edit again: Actually just creating one doesn't seem an option since that path is my top level for that directory as listed above so I'm not exactly clear how I'd go to that.

chente · 9. Mai 2023

ok, now run

chown :users /SSD/appdata

That should ensure that that folder is in the users group. And try to start the container.

Sorion · 9. Mai 2023

Zitat von chente

ok, now run
chown :users /SSD/appdata
That should ensure that that folder is in the users group. And try to start the container.

/SSD/appdata or /SSD ?

I did it for /SSD/appdata now - required a sudo and now it looks like this:

Code

$ ls -al /SSD/appdata
total 8
drwxrwsr-x 2 root users 4096 May  9 15:09 .
drwxr-xr-x 8 root root  4096 May  9 15:10 ..

So basically no change to what I posted earlier.

Oh and checking the container posts the same error.

chente · 9. Mai 2023

uff

Let's get it right. Delete the appdata folder. I guess it's empty right?

make sure you remove it

rm /SDD/appdata in CLI or from winscp, as you like.

Then go to the GUI and create a shared folder from there.

I have to leave now, in half an hour I'm back.

Change PUID on container after the install - Permission issues?

Sorion 9. Mai 2023

Jetzt mitmachen!

Ähnliche Themen

Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

[HowTo] Nvidia hardware transcoding on OMV 5 in a Plex docker container

Duplicati in docker: cannot browse subfolders when creating backup rule

SyncThing installation through Portainer not accessible via url

newbie container running problem with OMV5+Docker+rpi3

How to install Plex on OMV6 with docker image linuxserver/plex + On the fly transcoding files only in tmpfs (living on RAM not HDD)