Closed Marahin closed 2 years ago
In order to get past this issue, what I had to do is match uid
and gid
set in Dockerfile to the ones of my NFS user (1017). https://github.com/Marahin/zomboid-dedicated-server/commit/f322c954c4082c735b6b5a46c0c229b5971d0dd1
Is there any way to achieve that without having to resolve to build my custom image?
Hey, thanks for trying this out on K8S. I was meaning to give it a go, but never got around to it properly.
To be honest, I would say you are running into much the same issue that #19 and #24 are suffering from. I need to revise how I am handling folder permissions as there is definitely something going wrong between the SteamCMD base image, and the user actually deploying the Zomboid Container.
I am quite busy at the moment with other things, so I may not be able to address this particularly quickly. I would say that fixing the permissions issue will fix most of the problems people have been seeing.
If you have any ideas in the meantime, please feel free to make a PR on this or the SteamCMD repo that is reachable from my profile. 🙂
Is there any way to achieve that without having to resolve to build my custom image?
You should be able to override those if you set the build arguments for the Image.
And the worst you should have to do is to build the steamcmd-minimal image with your own IDs. Not ideal, I know. This is part of what I want to address.
Please comment or reopen if your issue still exists in the most recent version: 2.0.0
Describe the bug Hello! I am trying to deploy PZ using this image on Kubernetes (with storage being mounted through NFS), however the installation steps are failing.
To Reproduce Steps to reproduce the behavior:
/mnt/ssd-pool/zomboid
has two subdirectories:data
andconfig
, both set to chown 1017:1017 (zomboid:zomboid)Expected behavior Container starting up, eventually running the server.
Actual behavior Container fails to run
steamcmd.sh
due to lack of permissions (the script is owned bysteam:steam
user, and when I runid steam
within the container, it resolves to1000:1000
- while the container runtime is already set to1017:1017
, which iszomboid:zomboid
user).Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context Add any other context about the problem here.