search

RandomNinjaAtk / docker-lidarr-extended

lidarr-extended :: Lidarr application packaged with multiple scripts to provide additional functionality
GNU General Public License v3.0
275 stars 24 forks source link

[Bug]: /music appears to be mandatory #202

Closed telix5000 closed 1 year ago

telix5000 commented 1 year ago

I was consolidating my music libraries and removed /music from my docker compose. Upon spinning up my instance, I noticed /music was back; and after wiping it out and rebuilding it again, /music keeps coming back (to some default where no data is) -- but the documentation doesn't list it has a mandatory mount. I could very well move things back and map things accordingly, but I wanted to know if this is actually mandatory, a bug, or if it was some oversight as the mandatory /'s are all fairly well spelled out on the main page. Thanks.

RandomNinjaAtk commented 1 year ago

How is it showing up? Is it showing up in Lidarr as a root folder?

telix5000 commented 1 year ago

In Portainer I get this:

96bac9177337c27e58d8ce2430540ed93cc54c11acc26b494552afd34dae634d | /music

/music is not being used in the compose section, so it assigns this arbitrary mount to: /volume1/@docker/volumes/96bac9177337c27e58d8ce2430540ed93cc54c11acc26b494552afd34dae634d/_data

And in the Lidarr Status, you get /music; but obviously there isn't anything there.

RandomNinjaAtk commented 1 year ago

Latest changes should resolve it.... Keep in mind its untested because I do not have a similar environment to test with...

telix5000 commented 1 year ago

/music no longer appears. Thank you.