Volumes "server-data" and "server-files" are not used

[m4mfr3d]

Hello, I have set up the Docker container on my Synology NAS DS923+. However, if I specify the volumes "server-data" and "server-files", these are not used. The save data is still stored in the container. I extracted the container and found the save files at the following path: ...\image\home\steam\core-keeper-data

I haven't had this problem with other Docker containers yet.

The permissions for the folders are correct. Otherwise I would receive an error message in the logs or the container would not be able to write the storage files into the container.

Since I couldn't find a similar case through Google, I'm assuming it is an issue.

[arguser]

Hello @m4mfr3d I just created a server for testing this and I see the content inside the docker volumes. I'm using Docker Desktop on Windows + WSL

Maybe your system handles things differently?

[Micke90s]

@m4mfr3d Could you please post your docker-compose.yml? On which host system the container is running?

[m4mfr3d]

I don't use any docker-compose.yml. I'm using the Container Manager on Synology DSM 7.2.1.

[Micke90s]

The Container Manager should work similar to docker-compose.yml. It sounds like the mapping of the docker file path and the volume is missing.

services:
  core-keeper:
   ...
    #This is the mapping from the volume to docker file system 
    volumes:
      - server-files:/home/steam/core-keeper-dedicated
      - server-data:/home/steam/core-keeper-data
    ...
#This are the defined volumes
volumes: 
    server-files:
    server-data:

I would suspect that the Container Manager has some settings for the required server-data:/home/steam/core-keeper-data

[m4mfr3d]

Yes, I set the settings as follows: And the permissions are set to everyone - full:

I have also tested whether the mount is present and writable:

And the file has been saved:

[Micke90s]

The error seems to be in your first screenshot.

Please change the following way: /server-data => /home/steam/core-keeper-data /server-files => /home/steam/core-keeper-dedicated

This defines the path within the container. Which must have these values to work properly.

[m4mfr3d]

Ohh yes... Now it works. Maybe you could add that to the readme. Thank you @Micke90s