Persist configuration db and `playlists/` in Docker image

Currently we don't have a good way to actually persist `config.db` or potentially `playlists/` in a docker environment.

We should probably consider a smarter strategy on how and where we're saving our db files so we could provide a more cohesive solution.

Most Docker applications just have a directory/volume bind like `/config` and store everything there appropriately.