sparklyballs

volkion lidarr is the same as ours (using our baseimage in fact)

the ball is in radarr dev's court to mitigate against mono latest version they are aware of it

I'll take the vote of confidence but i just got the info from someone in a radarr git issue thread

for radarr "press enter to exit" loop try exec'ing in to the container and running cd /opt/radarr && curl -o - http://download.sonarr.tv/hotfixes/regression-mono-5.10/NLog.dll.gz | gunzip -c > NLog.dll and then restarting the container

both of the above questions would be better suited to asking lidarr dev team directly as they're both issues with the app itself rather than specifically our container you can either raise issues here https://github.com/lidarr/Lidarr or speak to them via their discord channel https://discord.gg/8Y7rDc9

there is no way to change to nightlies with our image in our experience nightlies often break more than they fix if you must use nightlies the Radar readme has a link to another image that uses nightlies should also add have no idea about whether you can migrate existing appdata to the nightlies docker and is certainly not something we support

this would be better off here https://lime-technology.com/forums/forum/47-docker-containers/

spin up the container and it's in the general section of the settings tab right at the top

@Sensei73 we have a separate repo for arm images refer to our main list here for available images list on the right is for armxx images and any ending --aarch64 are for aarch64 only

/Comics is not the same as /comics in linux you need to use /comics

you don't need the webui to use it it just makes pairing a remote and connecting to lastfm easier

building forked daapd from master and attempting to use it results in constant crashing and restarting of the service rendering it useless the release build of 25 does not contain webui and trying to access 3689 results in asking for user/login the current build uses that port in this manner (ie not for webui) https://github.com/ejurgensen/forked-daapd/blob/25.0/README.md#command-line-and-web-interface

me and the rest of the linuxserver team have clubbed together for an appointment with an optician for you lol

there's a PR just been merged to resolve this

Not likely as it stands currently as that requires compiling nginx adding that to the configure stage and we use the apk package manager version of nginx

Nice set of guides there

https://github.com/linuxserver/docker-letsencrypt#setting-up-the-application

you have multiple issues to resolve here in no particular order resolve the webui and container port clash ensure your dynamic dns address is updated otherwise the domain name won't resolve to your ip sort out port forwarding as without this nothing will function

no we stopped autoupdates on all our images with the exception of plex it created so many problems that outweighed any "benefit" and we switched to a weekly refresh model

I suggest you update your container because that update was made on 31st july this year https://github.com/linuxserver/docker-serviio/commit/22027ed68d66e2f1174b669a05b5da0e2a8d014c

I'm not certain that the update "corrupted" anything at all as to my knowledge this is the first time an update of the application has resulted in such a situation I'd rather say it was a compatibility issue between versions that lead to a "broken" database Gonna cite this post in the OP though

The change in source was made because currently streamboard site is dead. This is the alternative chosen https://launchpad.net/oscam and the last update was in august of this year.

The commits merged today for this image should fix this

you're confusing libreelec with this docker , there is no update folder because that is a Libreelec routine pure and simple. this headless docker has to be compiled from a patched version of the source code to run without window environment Leia is purely development at the moment and not entertaining doing builds for headless docker.

could be a nat reflection issue at the router level