Closed nomad64 closed 4 months ago
Hey @nomad64 - This change was to support dynamic UID/GID switching for other problems with QNAP and Synology NAS'ses.
If you now go ahead and create an edge-case thats based upon that 1 directory doesnt support no permission-changes im not sure how to help here. Im really trying to help everyone out, but some edge-cases are just to weird to be supported in a docker-image to be honest.
Possible solution: You could just go ahead and leave the directory local and the retention-policy mor conservative and use a cron/hourly to move the backups to the desired location.
Hey @nomad64 - Can this issue be closed?
@jammsen Sorry for the delay in getting back to you, life has been busy lately.
I understand the situation and that my setup is more of an edge case. I honestly can't remember why I setup squash for that mount and will have to revisit that config. In the interim, I simply removed the volume export for /palworld/backups
and will make some Ansible changes to move the files to the correct place on server shutdown.
Keep up the great work on this container! :+1:
Thanks, good luck, Happy to help!
Have you read the Important information text above
Current behavior
My current
docker-compose.yaml
file defines the following (I removed the game options for simplicity):Note that I export the backup volume to a different path. The destination is a Synology NAS NFS share that does not permit
chown
operations. The user running the container (1000) has permissions to write into that directory. When the container starts up, it tries tochown
the app directory, which includes the backup path. This operation fails and the container exits.Desired behavior
While the container files should be
chown
'd at startup to matchPUID
andPGID
, failures for the backup path should not cause the container to exit.Links to screenshots
No response
To Reproduce
Steps to reproduce the behavior:
/palworld/backups
directory redirected to a file system that does not allowchown
operations. This can be done viaall_squash
orroot_squash
.BACKUP_ENABLED
to trueSoftware setup
Hardware setup
Additional context
Container output: