[Bug Report] Issue with entrypoint when using NFS volumes

[SN4K3D]

You understand that if you dont provide clear information on your "Problem", "Software and Hardware-Setup" and the "Steps to reproduce" your issue will be closed without any help, because your not willing to do your part?

• [x] Yes i do!

You understand that im not a Game-Dev or Game-Server-Dev and my support is primary for the Docker-Image and somewhat limited to the Game-Server?

• [x] Yes i do!

Current behavior

Hello,

I am using your image in a Kubernetes infrastructure where volumes are mounted via NFS. For security reasons, the NFS mount is automatically set with nobody:users permissions. Even though I set the folder permissions on the NFS server to 1000:1000, the entrypoint script tries to run chown -R on these folders, which results in an error because the user does not have the necessary rights for this chown on the mounted volume.

Issue encountered The chown -R fails on NFS volumes mounted as nobody:users, even if permissions are set correctly on the NFS server. This blocks the container from starting.

Desired behavior

Expected behavior Ability to disable or skip the chown in the entrypoint script if the volume is mounted via NFS or if the operation is not possible. Or, at least, provide a workaround for this common use case on Kubernetes. Thank you in advance for your help and feedback on this topic. Please let me know if you need more information about the environment or configuration.

Links to screenshots

No response

Steps to reproduce

Steps to reproduce the behavior:

1. Mount/bind the volume data with share nfs and conf root_squash
2. Launch the container
3. see error

Software setup

• OS:
• Docker:

Hardware setup

• vCPU:
• RAM:
• Disk:

Additional context

No response

[jammsen]

Hey @SN4K3D - Sorry i didnt see this issue yet. Cant you just use uid 65534 for user nobody?

[SN4K3D]

Sorry for my late reply. If I use the user nobody, I cannot launch the container because it requires to be launched as root.

[jammsen]

Hey @SN4K3D - No, not what i mean, i dont think you understand me correctly. The container, yes, needs root, but it switches to a rootless command execution on the startup of the server. We need root to setup many things for nas/portainer and network compability, but then we use gosu and exec to start the server as the user you define here: https://github.com/jammsen/docker-palworld-dedicated-server/blob/develop/default.env#L2-L3 - Try to use there nobody and nogroup ids

[SN4K3D]

Hello, i have try this config and ok steam user change the puid and guid , but same probleme, the container try to chown the volume event if the user and groups are the same

[SN4K3D]

i have solved my probleme by override you'r entrypoint like this: