-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to keep server saves/config? #161
Comments
@InfernoZeus I apologize that that isn't something that's more cleat in the compose files. I'm actually working on updating all the examples so that they do save things by default. The updated compose file will look something like this:
But that only half solves your problem, It will save all the serverfiles (and in theory the save files) into a docker volume called Another option is to mount a local folder and have the server files written there. There is some details here on the different ways volumes can be mounted https://docs.docker.com/compose/compose-file/compose-file-v3/#volumes, But the simple suggestion is try something like this:
Years ago doing a local mount like that could cause some file permission issues if you were using docker on windows, I don't know if that's still the case. |
I just updated the main Readme document https://github.com/joshhsoj1902/linuxgsm-docker/blob/0.9.0/README.md And I updated the valheim compose file https://github.com/joshhsoj1902/linuxgsm-docker/blob/0.9.0/examples/docker-compose.valheim.yml |
@joshhsoj1902 Really appreciate the quick help on this. No need to apologise! I'm aware of how Docker works, and the distinction between named volumes and local folders, but I just couldn't work out which path inside the container I should be targeting. I'll give your new version a go 👍 |
I've been trying to use the example docker-compose files that you've got in this repository, but it's not clear to me how this preserves the save files and configuration for the game? (I'm trying to run Valheim, but I don't think it's a game specific question.) The only volume seems to be one for Log files, although even that wasn't working (I had to change from
logs
tolog
).Are there some other paths/volumes I could create so that they outlive the lifetime of the container created by docker-compose?
The text was updated successfully, but these errors were encountered: