Sebastian Schmidt

> I was having permission issues using this image, the problem was that `root` was the owner of `/palworld` which was causing the installation step to fail. > > This...

OMFG you mean "Named Volumes" NOW i get it, sorry i have a long line today 🤣 had very much other stuff to take care of and im totally exhausted,...

Need to take a look at this after i sleept sorry. 00:52 and still github maiils open 😑

I have change things out a little, please go ahead and test this too. See https://github.com/jammsen/docker-palworld-dedicated-server/commit/b6a116e66c4b5f5681e314d46bcff4102297c697 Commit-message: Restructured Dockerfile, less context-switching, less layers needed, improved security and formating, tested also...

> > Is there any way to handle running under a user thats not 1000? I tried chowning to a user ex. 1001 and the install fails. I tried passing...

Hello @kof8855 Because its considered Best-Practice in Docker and Docker-Compose to have your application not do that. Its called Stateless-Development with some tools, see here: https://12factor.net/config What you would ask...

Hey @Zer0mis - Please have a look at #40

Sorry for the big delay .... 😭 This issue should be solved with the commit and release from earlier today. You can find it here https://github.com/jammsen/docker-palworld-dedicated-server/commit/8546c890a518c99ab9be13b35a876c01ddaa7bde#diff-3b41cd2eeb76ac64c4b71b9cc6b253b358ab737f50d54e333b631ca27357e98e Im closing this issue...

This looks very interesting and very according to the Docker-Best-Practice way. There is also another PR from @gchai under #40 thats more focussed on very intensive script usage. Hmmm, both...

This solution is very Docker-Best-Practice way with using .env files to keep settings and secrets private. But its also fragile and very update heavy on the context of Pocketpair releasing...