search

jcorporation / myMPD

myMPD is a standalone and mobile friendly web mpd client with a tiny footprint and advanced features.
https://jcorporation.github.io/myMPD/
GNU General Public License v3.0
419 stars 65 forks source link

newly created myMPD container (1st run) is not able to create config files #661

Closed jcorporation closed 2 years ago

jcorporation commented 2 years ago

Not really... The issue is that newly created myMPD container (1st run) is not able to create config files (i.e. config, empty, pics, scripts, smartpls, ssl, state dirs and proper set of files inside) form env settings, when empty host dir is mapped to /var/lib/mympd. Instead it creates default config files. The same when docker volume is mapped to /var/lib/mympd When there is no mapping, all the files are created correctly according to env settings, but inside container. Seems like I found workaround. Let myMPD create defaults, then stop container, edit the files (for example http_port, ssl to false), and start container. When container is removed and recreated, the settings are kept as well. Not tried anything before 9.0.3. Currently mympd user is always 100:101, and the files are created with this ownership (which looks strange in debian, because user 100 and group 101 already exist as built-in)

Originally posted by @jacgl in https://github.com/jcorporation/myMPD/discussions/659#discussioncomment-1980055

jcorporation commented 2 years ago

Fixed with commit 626a802679a8f6345d30f0495fe5954698e649eb.