No way to configure user/group settings

[realies]

No way to configure user/group settings

[realies]

@bryab, what a strange coincidence :)

[realies]

Feel free to link to an example configuration or issue a pull request.

[blkqi]

An example is how LinuxServer.io does it here:

https://github.com/linuxserver/docker-baseimage-ubuntu/blob/master/Dockerfile#L35
https://github.com/linuxserver/docker-baseimage-ubuntu/blob/master/root/etc/cont-init.d/10-adduser

What do you think?

[xthursdayx]

+1

[realies]

Adding another user to run the app and have a configurable UID/GID would break the container configuration (mounted folders) for existing users that update. Any suggestions to go around that?

[blkqi]

Default PUID/PGID to 0 in Dockerfile. Later check /etc/passwd for an existing user (e.g. root) with those ID's. If one doesn't exist create a new one with a generic name.

Not the cleanest example, but the general idea is sound: https://github.com/coppit/docker-inotify-command/blob/master/runas.sh

I should apologize... I would be more useful if I could, but this docker stuff is still new to me.

[realies]

That logic would also have to reconfigure the supervisor configuration based on the active user.

[Djeremaille]

+1

[bryab]

I have implemented this in my fork. But it required me to change the paths from /root to a new folder, which i named /slsk. Let me know if you all have any advice here, but this works for me. You must set both PUID and PGID environment variables.

bryab@f586cce

[apurvis]

having an issue where the container is working great but doesn't seem to respect PUID and PGID when writing files. my env vars are:

PUID=1027
PGID=100
UMASK=0002

from a shell inside the container files appear to be owned by root and also have no permissions.

---------- 1 root root 1782057 May 19 03:23 '02 citys of refuge.mp3'

this is odd because the init.sh script did manage to create a soulseek user in etc/passwd in the container:

soulseek:x:1027:100::/data:/bin/false

but in the end that's not a huge deal to me... what is kind of a big deal to me is that from a terminal on the machine files appear to be owned by root and have all permissions:

-rwxrwxrwx+ 1 root root 150274770 May 18 22:51 'SHXCXCHCXSH - XLR8R Podcast 574, 201901.mp3'

giving execute permission to files written to the machine from a file sharing network is... alarming, let's say.

am i doing something stupid or is there a legitimate issue here?

FWIW i am running this docker image inside synology's docker app