Server Data not persistent after docker down

[Varusal]

After running docker compose down and then using docker compose up -d all players start with a new fresh player character.

/opt/vintagestory shows the player and world data.
Still after restarting the server, all progress is lost.

version: '3.8'

services:
  vintagestory-server:
    image: ghcr.io/darkmatterproductions/vintagestory:latest
    container_name: vintagestory-server
    ports:
      - "42420:42420/tcp"
      - "42420:42420/udp"
    volumes:
      - /opt/vintagestory:/vintagestory/data
    environment:
      - ENABLE_DEBUG_LOGGING=false
      - ENABLE_CHAT_LOGGING=true
      - VS_CFG_SERVER_NAME=My Vintage Story Server
      - VS_CFG_MAX_CLIENTS=16
      - VS_CFG_ENFORCE_WHITELIST=1
    restart: unless-stopped

[Ralnoc]

@Varusal - Can you add the log output from your container to the issue? This is a Docker process, not one managed by the container. I need to see what it is doing with you install.

[Varusal]

Hi there,
sorry for the very late response.

Here is the docker log.
You will also notice that the log starts on the 03.03 but then suddenly it continues with 15.03. Not sure why this is the case (the server was offline from 03.03 till 15.03)

vintagestoryDockerLog.txt

[Ralnoc]

Seems to be contagious. For some reason the system didn't notify me that you responded.

I'm looking over the log. That date shift in the startup logs is odd, but I don't think it is relevant to the issue you were seeing. Can you confirm that /opt/vintagestory is owned by 1100? Just run chown -R 1100:1100 /opt/vintagestory and then restart the docker container. The only thing I can think of, based on what you have shared, is that.

[Thermitenjoyer]

Just to add to this - I'm also experiencing this issue, wonder if it's related to my rcon config issue?

I did notice whenever closing the container it exits with code 137 instead of code 0 like I'm used to.

[Varusal]

Hi there,

sorry for the late response I'm currently moving apartments :)

Seems to be contagious. For some reason the system didn't notify me that you responded.

I'm looking over the log. That date shift in the startup logs is odd, but I don't think it is relevant to the issue you were seeing. Can you confirm that /opt/vintagestory is owned by 1100? Just run chown -R 1100:1100 /opt/vintagestory and then restart the docker container. The only thing I can think of, based on what you have shared, is that.

That seems to be already the case and the result is the same.