Setting UID / PID can have big issues on shared servers

[Webrow]

Hey,

Setting UID / PID can have major issues (in my case all files of the server are owned by another user, if you are not able to sudo you will be unable to chown the files. Might it be an idea to introduce a user created in the alpine image and from there connect it. Yes itll cause write / read issues during copying of savegames into temp, but isnt that how it is supposed to work (or maybe use whoami to determine who is building the Dockerfile instead of hardcoding it?)

[MattPark]

It's fixed in latest. See #16. You can set to whatever you need to using PGID/PUID env variable

[Webrow]

Hey Matt, its not regarding the matter that its fixed, just that it defaults to 1000. 1000 is not always your own user, and knowing it later on can cause bigger issues. (I assume 1000 was chosen cause often its the first user). Nevertheless its a nitpick. Ill close it!

[MattPark]

Yeah I mean I see your point though. 1000:1000 was not a real user or group on my system. The ideal default should probably be the result of id -u and id -g ... not a huge deal since this fix gives everyone the option whereas option was missing before.

[Webrow]

Agreed Op wo 10 feb. 2021 00:06 schreef Matt Park <notifications@github.com>:

…

Yeah I mean I see your point though. Like ideal default should be the result of id -u and id -g probably ... not a huge deal since this fix gives everyone the option whereas option was missing before. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#23 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYH27KYXJ66AUXXNQU4X3LS6G5YHANCNFSM4XL2GIUA> .