Closed haldi4803 closed 11 months ago
The GameVault Server runs with a non-root user (1000:1000), but this user doesn't have the necessary permissions to access the mapped files volume or the images volume in the container.
To resolve this, consider the following recommended solutions:
Grant specific permissions to the mapped folders on your host machine:
chown -R 1000:1000 /the/folder/you/map/on/your/host/
Run the GameVault Server as a user with the required permissions. For instance, you can use root by setting the PUID (User ID) and PGID (Group ID) environment variables to 0.
If security allows, you can make the folder accessible to all users on Linux, although this is not advised due to potential security risks:
chmod -R 777 /the/folder/you/map/on/your/host/
Choose the option that aligns with your security and permission requirements.
Or, use the environment variable to set PUID PGID to an existing user...
But that's not the issue here. The docker container should not infinitely reboot simply because he has no permissions for the folder. Right?
The container has no reason to live and dies due to permission checks upon startup. As for the infinite reboot, if you set your restart policy to restart-always, it's on you.
Did you fix the permissions and get it running?
Yes.
Awesome
Describe the bug Container doesn't start up! Reboots.
To Reproduce No File Access in Container
Expected behavior Server Starts Web Interface at least.
Server: Docker Container.
Log