I stumbled through the config for them and they worked, so I didn't spend a lot more time on them, but the configs have been wrong all this time. That is kind of how this started.I tried several media servers - minidlna worked fine until I got my roku devices.those needed some transcoding ability. Squid - thanks for clarifying that you CAN point these to a UD data storage 's nice to be able to deploy a docker to a temporary device to "try it out" and if you don't want to keep it, remove it from unraid, format the USB device and you're done. Is there an easy way to destroy the appdata share created on Disk 2? I'll know in a bit, if drive 2 spins down.no worries. (Probably on the disk with the most space at the time.) Bah! Humbug!ĭo these look like they have been reassigned correctly? The dockers restarted without an error after the modification. I guess it put it where it liked (it WAS "required") and I didn't catch it until now.
At least that solves the mystery.Īttached are the two screenshots in the hope that this might help someone contemplating a similar move.īTW, do you know if there is any way to relocate this for the time being to the Unassigned Disk share, just is it possible? I know you could choose NO for the cache disk option, but I don't know if that allows you to use a UD share.įunny thing - I totally missed that Serviio makes reference to a config path, but I did not have one directly assigned. This says that disk 2 is where the data for both of my dockers reside, so it makes sense that while the docker is active, the disk will be polled, even if there is no one watching anything.
Serviio login install#
So, when I do my upgrade, I guess one of the checkboxes for me is to install an actual Cache disk - at least then I can select it. I cannot choose the Unassigned Disk share. Looks like you're right on the doesn't appear to be possible to relocate this to the UD share I created.the only options in the dropdown are Disks 1 2 or 3. I attached my diagnostics, is there something else I might try? I have had this issue present in at least the previous two versions of the docker - I am running 1.9 currently. I did try giving the app "privileged" access but it didn't do anything about the drives being spun up (as a matter of fact, it spun them ALL up!) executing container initialization scripts. ensuring user provided files have correct perms.exited 0.
making user provided files available at /var/run/s6/etc.exited 0. I looked in the logs for Serviio from the WebGUI and there is nothing there that is unusual: Restart the docker and they return to being polled. Stop the Serviio docker and you can spin them down manually and they stay spun down. My Drive 2 and my Parity drive will not spin down. Everything works as expected, but I have noticed something odd since I installed the Serviio docker. I'd like to first say thanks for this wonderful docker.
0 kommentar(er)
