VRising Wine folder not owned

[Kiliki_Kiliki]

OS Name/Version: Ubuntu 22.04

Product Name/Version: v2.5.1.8, built 17/09/2024 12:32

Problem Description:
Im creating a VRising Server with Docker Wine with an external Datastore which is mounted via nfs upon installation i get even though every other file generated successfully

wine: '/AMP/v-rising' is not owned by you, refusing to create a configuration directory there

Steps to reproduce:
Try installing VRising Server with Docker on linux via Datastore mounted with NFS

Steps taken to resolve:
Another server is running just fine on the same Datastore (different game tho) so it appears to be a wine problem

[Greelan]

Is the other instance in docker? Might be an issue with how the datastore is being mounted into the container

[Kiliki_Kiliki]

Yeah the other Instance is also in a Docker Container and is Satisfactory precisly but i think its just a wine issue which requests more permissions than necessary ^^’

[Greelan]

You could exec into the container and see what the perms are for that directory. Would be interesting to compare with an instance that is not installed on a NFS mount

[Greelan]

For example, on one of my instances:

ls -la /AMP/v-rising/
total 35
drwxr-xr-x  9 amp amp     13 Oct  3 08:51 .
drwx------ 10 amp amp     37 Oct  3 08:50 ..
drwxr-xr-x  6 amp amp     22 Oct  3 08:51 1829350
-rw-r--r--  1 amp amp     92 Oct  3 08:51 .autoExclude
drwxr-xr-x  2 amp amp     10 Oct  3 08:50 linux32
drwxr-xr-x  2 amp amp      3 Oct  3 08:50 linux64
drwxr-xr-x  2 amp amp      8 Oct  3 08:50 package
drwxr-xr-x  2 amp amp     32 Oct  3 08:50 public
drwxr-xr-x  6 amp amp      7 Oct  3 08:50 siteserverui
-rwxr-xr-x  1 amp amp   2359 Jan 31  2024 steamcmd.sh
drwxr-xr-x  4 amp amp     10 Oct  3 08:51 .wine
-rw-r--r--  1 amp amp   1024 Oct  3 08:51 winescript_log.txt
-rwxr-xr-x  1 amp amp 841673 Oct  3 08:50 winetricks

[Kiliki_Kiliki]

this is an old vrising instance which is on the native datastore

this is the new instance on the new datastore

which is very strange

but i found this video here https://www.youtube.com/watch?v=Ul3dFZM8fW4
which illustrates the same issue with wine and linux just not related to docker and amp but has the same error code

is is somehow possible i modify the setup process for that instance or maybe it should get fixed on the amp side even though a niche issue?

[Greelan]

What are the perms of the v-rising directory on the host?

[Kiliki_Kiliki]

Im not sure what you mean by that the first screenshot is amp account just over sftp but i can send it over the command line but lemme know if i understand it wrong

so this is the old instance which worked fine on the default datastore also in docker and through wine it has the same permissions as the new Instance with the new Datastore

[Greelan]

OK. Just to be clear, I asked originally for the perms inside the docker container. You can get into the container with:

docker exec -it AMP_INSTANCENAME bash

(Substitute INSTANCENAME as appropriate.)

Then check the perms.

But if the NFS mountpoint perms on the host is what you showed in the second screenshot, then that is the issue. Have you tried chowning the mountpoint with amp:amp?

[Kiliki_Kiliki]

Well thanks for the direction ^^’ found a hacky solution where i set the nfs id remapping to the same id as my amp user now it works
Ty for you help and have a great day

(if anyone else has the problem modify the /etc/exports line of you nfs host to include anonuid=AMPUSERID,anongid=AMPGROUPID
was 1000 1000 for me but may differ for u )