Post Reply 
MinimServer 2 in Docker - best approach for persistent config?
27-12-2020, 23:55
Post: #1
MinimServer 2 in Docker - best approach for persistent config?
Firstly, big thanks for creating MinimServer - I've used the older versions for ages and have now decided to do things 'properly' and both buy a full license, and install v2 in a Dockerised environment.

However, I'm unsure what the best practice is to achieve persistent configuration. I followed the instructions on generic Docker setup, and concluded that following the instructions word-for-word would result in configuration being lost after a container restart, i.e. /opt/minimserver/data would be transient and not last beyond the container's lifetime.

So I added the data directory as a read/write persistent volume in my compose file:

Code:
version: "3"
services:
  server:
    image: minimworld/minimserver:2.0.16
    network_mode: host
    environment:
      - TZ=Europe/London
    volumes:
      - /path/to/minimserver/data:/opt/minimserver/data
      - /path/to/music:/Music:ro

This fixes things for now, but seems sub-optimal:
  • The directory also contains logfiles in addition to config, and I'm not sure if they should be shared.
  • The directory contains a pid file, which probably shouldn't need to survive container restart.

The Synology/QNAP guides mention mounting a /MinimServer directory, but it's apparently read-only, and I'm unsure what it should contain in a general-purpose Docker setup.

What is the recommended way to achieve persistent configuration for a Dockerised setup?

Many thanks.


P.S. I got this wrong initially and the transient config ate one of my license activations Angry. Hope it can be reset!
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
MinimServer 2 in Docker - best approach for persistent config? - mr_smidge - 27-12-2020 23:55

Forum Jump:


User(s) browsing this thread: 1 Guest(s)