Closed lightlike closed 2 years ago
When you say /home/steam/.avorion/galaxies/avorion_galaxy
, are you referring to the dir inside the container or is that the path you have mounted on the host?
The only thing that comes to mind is to double check that you don't have a typo in your volume mounts.
That is the directory inside the container. Everything is correctly generated on first run but every subsequent restart overrides all manual changes to every file inside the folder.
Are you modifying the files by making change inside the container directly or are you making changes on the host and mounting that with the -v
option?
I am making changes from outside the container. Specifically using smb/cifs. Both the data and backups are mounted via docker-compose volumes.
I'm at a loss then. It seems like it's a docker config issue, but I don't know.
Does it work properly if you try a temp container via the docker cli and a local bind mount?
mkdir /host/tmp/path
docker run --rm --name avorion -v /host/tmp/path:/home/steam/.avorion/galaxies/avorion_galaxy rfvgyhn/avorion
/host/tmp/path
docker run --rm --name avorion -v /host/tmp/path:/home/steam/.avorion/galaxies/avorion_galaxy rfvgyhn/avorion
That seems to work. Hmmmmmm. Maybe I did those changes while the Server was still running and it overrode them when shutting down. I will try some stuff out.
Every time the container restarts, it completely overwrites every file in the '/home/steam/.avorion/galaxies/avorion_galaxy' directory. I tested this with the server.ini, admin.xml and whitelist.txt.
I am using the default docker configuration given in the Repository. Nothing fancy as I am only thrying the server out to really use later except the --admin argument.
Permissions on the entire directory are user: 1000:1000 and mask: 770
Any idea why this is happening or how I can fix this.