UID and GID Specification

[kylepauljohnson]

Good afternoon, thanks for the work on this container. Been running it without persistence for a bit and it's worked great. Recently I have been working to get it setup to utilize the config directory so it can resume from autosave however I am having trouble configuring it to run as a proper user that has permissions to the folder.

I am running Docker from my Synology NAS and have many other containers I run which generally take PUID and GUID or UID and GID property that can be set as an environment variables to specify the user. Looking through the documentation and code it doesn't appear this container supports that.

Any chance that could be added?

[Highcooley]

Same here, this would be greatly appreciated

[duckfullstop]

Shouldn't be a problem to add this! I'm a little busy over the next couple days due to life stuff, but I'll see if I can get around to it next week.

(otherwise if someone wants to submit a PR, then all power to you!)

[Ultre00]

Same here would love this change. Unable to save now in my Synology NAS setup. Is it possible to get saves working without the PUID and GUID?

Could anyone explain why it isn't enough to just create a user called openttd with read / write permissions?

docker_openttd/Dockerfile

Line 79 in 49f64cd

RUN chown -R openttd:openttd /config /app

Doesn't this map the openttd user to the openttd user of the volume?

[duckfullstop]

Is there any further interest in a new PR from anyone? I can potentially take a look into doing it myself at some point, but I'm a bit busy with other goings on.

[duckfullstop]

Thanks to @flexd for #26 - however I'm inclined to not merge it as functionality appears to be working properly if you override the UID/GID in your container runtime (e.g --user {uid}:{gid} in docker / podman CLI, etc).

Can someone check this and report back (either here or in the PR) as to whether we still need the ability to override in the envvar?