3 ms·
How does persistent state work with this? For example, what happens to my saved games? What if I update the image (for example to pick up a Steam update)? What
by rlpb 10y ago
How does persistent state work with this? For example, what happens to my saved games? What if I update the image (for example to pick up a Steam update)? What will happen to those saved games?
- nostrebored 10y agoMount volumes that correspond to save locations. The volume should be persistent so even if the image changes the data will remain.
- rlpb 10y agoAren't save locations different on a per-game basis? So does this need configuration? If not, then how does it work without user intervention?
- nostrebored 10y agoIf you don't want to do something smarter, by nature of the file system that Steam rests on, there must necessarily exist some folder s.t. all save locations exist in a subfolder (recursive) of this folder. You'll use extra space, but you can definitely do that easily. Alternatively, you can keep an environment variable GAME_SAVE_MOUNTS to which you append a -v flag with the desired mount saves. You can that start your container with $GAME_SAVE_MOUNTS and have everything work out of the box.
- arno1 10y agoCurrently it is stored in a docker volume. (the data available at /var/lib/docker/volumes path) But changing just one line in a docker-compose.yml file you can mount it wherever you want on your host. See "data:/home" in there. You can write there "/home/your-user/mysteamdata:/home", so that all Steam games (caches, saves, ...) will be available for you at your home directory in "mysteamdata" directory ;-)