JesterEE

@GuildDarts It might also make sense to incorporate a "pass-through" option for the WebUI and WebUI New tab; one that uses a Docker's configured WebUI setting rather than re-specifying it for the plugin. Kinda like the way you already have the Docker Sub Menus for the selected images, but instead of the submenu, a quick link to the WebUI subcommand. This won't actually work for my use case, with the way Unraid currently handles WebUIs with mapped container networks ... so I'd also like to keep my original request intact 😉. As of Unraid 6.8.3, if you specify a container as the Network Type, it will not allow the WebUI subcommand to be present even if it is specified in the configuration. So, this might break a look-up of the WebUI subcommand if you attempt to look for it in the submenu instead of parsing the XML. I haven't looked at your plugin code, so I don't know how you're doing it. -JesterEE

I have another enhancement request. Sorry ... I've been playing 😒. When selecting a Docker Restart option, only restart the containers that are already started. Currently, it will restart containers that are on and start containers that are off. -JesterEE

Good question ... honestly IDK. Maybe others that have been around for longer than I have can share some historically significant info about that. The help information for the Docker WebUI element says to do it this way, and the request of [PORT:####] syntax is just to align with the base functionality. -JesterEE

Thanks for the great plugin! Can I make 2 enhancement requests? Allow renaming of Folders after they have been created. Currently, the name is grayed out for editing after initial creation. Allow the Unraid Docker WebUI construct of [IP] and [PORT:####] for buttons in the Folder. for example WebUI button = https://[IP]:[PORT:1234] -JesterEE

@linuxserver.io Thread and app need to be updated to the new locations. https://github.com/linuxserver/docker-nzbhydra2 https://hub.docker.com/r/linuxserver/nzbhydra2

Can not confirm your issue with the latest. Works as expected on my box.

@Squid Thanks for this great plugin. Can I request an update for those of us running Unraid 6.8.3 that use docker container to container networking? @bonienl updated the docker logic to trigger an update of docker images that depend on the network of another docker image that has been updated. I believe this logic is triggered in the php code, so the docker page needs to be loaded to allow this to happen. Is it possible to have the plugin "load the docker page" to allow this to happen after the docker auto update is executed? Thanks! -JesterEE

I started using this container this week. I have not run a CPU taxing container like this before and found an interesting thing that might be applicable to others. I have half my CPU cores available to Unraid and half isolated for VMs. Making the isolcpu system initialization change does not modify how the CPU is reported to the docker process and the containers that are run. For example, my 8C/16T AMD 3800X still reports as such even though only 4C/8T are available for allocation by the host (and by extension, docker). So, when running the BOINC container and letting it use 100% on my CPU, it spins up 16 WU processes because it thinks it can do that many on the processor concurrently without multitasking on the same core. The result, each core has 2 BOINC threads competing for resources. Probably not the biggest deal, but not ideal as there is still likely overhead switching between them. So, in instances where you isolate CPUs away from the host, my workaround is to tell BOINC the percentage of the CPU still available to it (i.e. how many are still available for docker allocation ... e.g. [16/2]/16 = 8/16 = 0.5, 0.5*100=50%). This setting is in: Options->Computing Preferences->Computing->Usage limits->Use at most '50%' of the CPUs. I tried CPU pinning cores to the BOINC docker and keeping the BOINC config at 100%, but BOINC still interprets the number of cores from the CPU definition. Anyone have a better solution that is more portable and less hardcoded to the current system configuration? I don't always run CPU isolation and would like to keep as much as possible immune to my whim to change it. -JesterEE

@linuxserver.io Thank you for making this application available to the Unraid community! Great work as always! I think we all should be running F@H with our always on machines now more than ever as we fight COVID-19 if you can spare the clock cycles, and we each individually can justify the extra cost of the higher power draw and component degradation. For those that may not want to run this container because it might "steal" compute resources from the server tasks, be advised that the docker app will run the CPU folding processes with a nice level of 19 (i.e. a LOW scheduler priority). So, this is not an issue and everything else on the system will have a CPU priority higher than the folding tasks even when operating in "Full Power" mode. The GPU doesn't work on a scheduler like the CPU, so yes, the GPU will work hard. BUT, I was able to fold and run 10+ Plex hardware transcoded streams on my GTX 1060 6GB card at the same time. So really, it's a non-issue as well. There's more than enough juice to go around! Hope this alleviates some concern! Join the UnRAID folding team and do your part! Service guarantees citizenship! UnRAID Folding Team: 227802 -JesterEE

After installing the plugin, I receive the following error in the system terminal upon starting Unraid. error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory This does not get logged in the syslog ... only output to an attached terminal. I have had this error since Unraid 6.8.0 but I just traced it here on a new 6.8.3 install. This has been experienced by other users too, but up till now, no one knew what was causing it. -JesterEE

No problem. FYI, I temporarily uninstalled the GPU Statistics plugin till this gets sorted out. This output is without the plugin installed. <?xml version="1.0" ?> <!DOCTYPE nvidia_smi_log SYSTEM "nvsmi_device_v10.dtd"> <nvidia_smi_log> <timestamp>Thu Mar 19 21:10:15 2020</timestamp> <driver_version>440.59</driver_version> <cuda_version>10.2</cuda_version> <attached_gpus>1</attached_gpus> <gpu id="00000000:09:00.0"> <product_name>GeForce GTX 1060 6GB</product_name> <product_brand>GeForce</product_brand> <display_mode>Enabled</display_mode> <display_active>Disabled</display_active> <persistence_mode>Disabled</persistence_mode> <accounting_mode>Disabled</accounting_mode> <accounting_mode_buffer_size>4000</accounting_mode_buffer_size> <driver_model> <current_dm>N/A</current_dm> <pending_dm>N/A</pending_dm> </driver_model> <serial>N/A</serial> <uuid>GPU-36d93047-20d4-1f53-260a-613eac368c41</uuid> <minor_number>0</minor_number> <vbios_version>86.06.0E.00.99</vbios_version> <multigpu_board>No</multigpu_board> <board_id>0x900</board_id> <gpu_part_number>N/A</gpu_part_number> <inforom_version> <img_version>G001.0000.01.03</img_version> <oem_object>1.1</oem_object> <ecc_object>N/A</ecc_object> <pwr_object>N/A</pwr_object> </inforom_version> <gpu_operation_mode> <current_gom>N/A</current_gom> <pending_gom>N/A</pending_gom> </gpu_operation_mode> <gpu_virtualization_mode> <virtualization_mode>None</virtualization_mode> <host_vgpu_mode>N/A</host_vgpu_mode> </gpu_virtualization_mode> <ibmnpu> <relaxed_ordering_mode>N/A</relaxed_ordering_mode> </ibmnpu> <pci> <pci_bus>09</pci_bus> <pci_device>00</pci_device> <pci_domain>0000</pci_domain> <pci_device_id>1C0310DE</pci_device_id> <pci_bus_id>00000000:09:00.0</pci_bus_id> <pci_sub_system_id>371A1458</pci_sub_system_id> <pci_gpu_link_info> <pcie_gen> <max_link_gen>3</max_link_gen> <current_link_gen>3</current_link_gen> </pcie_gen> <link_widths> <max_link_width>16x</max_link_width> <current_link_width>16x</current_link_width> </link_widths> </pci_gpu_link_info> <pci_bridge_chip> <bridge_chip_type>N/A</bridge_chip_type> <bridge_chip_fw>N/A</bridge_chip_fw> </pci_bridge_chip> <replay_counter>0</replay_counter> <replay_rollover_counter>0</replay_rollover_counter> <tx_util>0 KB/s</tx_util> <rx_util>0 KB/s</rx_util> </pci> <fan_speed>0 %</fan_speed> <performance_state>P0</performance_state> <clocks_throttle_reasons> <clocks_throttle_reason_gpu_idle>Not Active</clocks_throttle_reason_gpu_idle> <clocks_throttle_reason_applications_clocks_setting>Not Active</clocks_throttle_reason_applications_clocks_setting> <clocks_throttle_reason_sw_power_cap>Active</clocks_throttle_reason_sw_power_cap> <clocks_throttle_reason_hw_slowdown>Not Active</clocks_throttle_reason_hw_slowdown> <clocks_throttle_reason_hw_thermal_slowdown>Not Active</clocks_throttle_reason_hw_thermal_slowdown> <clocks_throttle_reason_hw_power_brake_slowdown>Not Active</clocks_throttle_reason_hw_power_brake_slowdown> <clocks_throttle_reason_sync_boost>Not Active</clocks_throttle_reason_sync_boost> <clocks_throttle_reason_sw_thermal_slowdown>Not Active</clocks_throttle_reason_sw_thermal_slowdown> <clocks_throttle_reason_display_clocks_setting>Not Active</clocks_throttle_reason_display_clocks_setting> </clocks_throttle_reasons> <fb_memory_usage> <total>6077 MiB</total> <used>0 MiB</used> <free>6077 MiB</free> </fb_memory_usage> <bar1_memory_usage> <total>256 MiB</total> <used>2 MiB</used> <free>254 MiB</free> </bar1_memory_usage> <compute_mode>Default</compute_mode> <utilization> <gpu_util>2 %</gpu_util> <memory_util>0 %</memory_util> <encoder_util>0 %</encoder_util> <decoder_util>0 %</decoder_util> </utilization> <encoder_stats> <session_count>0</session_count> <average_fps>0</average_fps> <average_latency>0</average_latency> </encoder_stats> <fbc_stats> <session_count>0</session_count> <average_fps>0</average_fps> <average_latency>0</average_latency> </fbc_stats> <ecc_mode> <current_ecc>N/A</current_ecc> <pending_ecc>N/A</pending_ecc> </ecc_mode> <ecc_errors> <volatile> <single_bit> <device_memory>N/A</device_memory> <register_file>N/A</register_file> <l1_cache>N/A</l1_cache> <l2_cache>N/A</l2_cache> <texture_memory>N/A</texture_memory> <texture_shm>N/A</texture_shm> <cbu>N/A</cbu> <total>N/A</total> </single_bit> <double_bit> <device_memory>N/A</device_memory> <register_file>N/A</register_file> <l1_cache>N/A</l1_cache> <l2_cache>N/A</l2_cache> <texture_memory>N/A</texture_memory> <texture_shm>N/A</texture_shm> <cbu>N/A</cbu> <total>N/A</total> </double_bit> </volatile> <aggregate> <single_bit> <device_memory>N/A</device_memory> <register_file>N/A</register_file> <l1_cache>N/A</l1_cache> <l2_cache>N/A</l2_cache> <texture_memory>N/A</texture_memory> <texture_shm>N/A</texture_shm> <cbu>N/A</cbu> <total>N/A</total> </single_bit> <double_bit> <device_memory>N/A</device_memory> <register_file>N/A</register_file> <l1_cache>N/A</l1_cache> <l2_cache>N/A</l2_cache> <texture_memory>N/A</texture_memory> <texture_shm>N/A</texture_shm> <cbu>N/A</cbu> <total>N/A</total> </double_bit> </aggregate> </ecc_errors> <retired_pages> <multiple_single_bit_retirement> <retired_count>N/A</retired_count> <retired_pagelist>N/A</retired_pagelist> </multiple_single_bit_retirement> <double_bit_retirement> <retired_count>N/A</retired_count> <retired_pagelist>N/A</retired_pagelist> </double_bit_retirement> <pending_blacklist>N/A</pending_blacklist> <pending_retirement>N/A</pending_retirement> </retired_pages> <temperature> <gpu_temp>51 C</gpu_temp> <gpu_temp_max_threshold>102 C</gpu_temp_max_threshold> <gpu_temp_slow_threshold>99 C</gpu_temp_slow_threshold> <gpu_temp_max_gpu_threshold>N/A</gpu_temp_max_gpu_threshold> <memory_temp>N/A</memory_temp> <gpu_temp_max_mem_threshold>N/A</gpu_temp_max_mem_threshold> </temperature> <power_readings> <power_state>P0</power_state> <power_management>Supported</power_management> <power_draw>28.83 W</power_draw> <power_limit>120.00 W</power_limit> <default_power_limit>120.00 W</default_power_limit> <enforced_power_limit>120.00 W</enforced_power_limit> <min_power_limit>60.00 W</min_power_limit> <max_power_limit>140.00 W</max_power_limit> </power_readings> <clocks> <graphics_clock>455 MHz</graphics_clock> <sm_clock>455 MHz</sm_clock> <mem_clock>4006 MHz</mem_clock> <video_clock>696 MHz</video_clock> </clocks> <applications_clocks> <graphics_clock>N/A</graphics_clock> <mem_clock>N/A</mem_clock> </applications_clocks> <default_applications_clocks> <graphics_clock>N/A</graphics_clock> <mem_clock>N/A</mem_clock> </default_applications_clocks> <max_clocks> <graphics_clock>1961 MHz</graphics_clock> <sm_clock>1961 MHz</sm_clock> <mem_clock>4004 MHz</mem_clock> <video_clock>1708 MHz</video_clock> </max_clocks> <max_customer_boost_clocks> <graphics_clock>N/A</graphics_clock> </max_customer_boost_clocks> <clock_policy> <auto_boost>N/A</auto_boost> <auto_boost_default>N/A</auto_boost_default> </clock_policy> <supported_clocks>N/A</supported_clocks> <processes> </processes> <accounted_processes> </accounted_processes> </gpu> </nvidia_smi_log>

Yes

@b3rs3rk Issue using the GPU Statistics plugin with the Unraid 6.8.3 LinuxServerio NVIDIA Build. I don't think it's specifically a GPU Stats plugin error ... but appears frequently when the plugin is in use. Just to keep you in the loop.

@JaseNZ @mlapaglia

Anyone using this kernel with a Nvidia GPU VM passthrough? A VM will start once, but if restarting the VM, or starting another which uses the GPU, the VM will start but I will get no signal from the card. I need to restart the server to get any signal again. Was trying this kernel for the audio passthrough on the x570. Was this the issue that caused Limetech to pull the NAVI patch from the 6.8.0-RCs? -JesterEE

From Unraid 6.8.0-RC7 root@Tower:~# /usr/bin/sensors -A k10temp-pci-00c3 CPU Temp: +61.4°C (high = +70.0°C) MB Temp: +61.4°C -JesterEE

Quick update: I was working with another build of Unraid that allows the temperatures to be read by the temp sensors plugin and ControlR started working correctly ... confirming the bug.

SSH into your server, transcode something, watch to see where the files go. If they don't go into your /tmp directory you did it wrong.

@labbz0re @Jake G I'd like to know how you are trying to do this ... Windows doesn't have a 2.0 release. If you're asking if you can use 1.3.X to 2.0.X the answer is no and it's not an Unraid/docker issue.

Unfortunately, the trend in 2020 computing does not favor our collective need for a reasonably sized, quiet, mid/full-ATX chassis with LOTS of mounting locations to accommodate mass storage solutions. It simply doesn't exist ... and really, TBH, it never really did. Fitting 3x 3.5" to 5.25" bay cages for 15 total drives in a tower has always been a workaround, and a pretty expensive one at that when each cage can cost $50-$150! By the time you configure the chassis with the required bays and cooling, you're looking at, at least, $350 ... and that's if you really try hard not to overspend! That's more than I'm willing to drop on a bad solution to a niche problem, but I can't speak for everyone. Also, IMHO, most of the chassis that accommodate these builds are ugly! Even if they were/are reasonably priced, I would not want to build in them even if it is going to sit in the corner or a closet. The notable exception, the Silverstone Temjin TJ11. But at $350 when it was released ~2014 ... and $750 now for the few places that have 1 or 2 left in the back of the stockroom, this was ALWAYS an expensive build. And to uglify it with hot-swappable cages, to me, seems like a sin. Also, a nod to @Harro's functional build. I'd love to find an original Cooler Master Centurion 590 in a dumpster or Good Will somewhere 🤣! Going forward I think we all need to bite the bullet and realize this is just not going to happen unless the winds change direction and personal storage solutions that don't include overpriced and under-powered systems (*cough* Synology) become common place. I think most people that find this thread know that there are server grade racked solutions out there with reasonable second hand prices. But, for someone that really wants to keep their build to a workstation, this is not an option. It even bugs me a little when people flippantly post something like, "just buy a used 4U server ... 24+ bays, problem solved." Not helpful ... at all! If "we" wanted a 26"-30" deep, 100+ lb. tank with jagged corners and awful non-racked standing solutions that sounds like a jet engine ... then yes, problem solved! But, "we" don't. I don't intend to ignite a flame war here ... but after all, this thread is for tower cases. It says it right in the title. Why are people even bringing up rack solutions? I'll give a pass to those recommending casters for rack chassis though. Not what I'm after, but OK. I contacted 45 Drives about their Storonator Workstation. I was pretty sure they only sell them as a configured solution, and they don't post the chassis dimensions, but it couldn't hurt to ask when it has space for 11x 3.5" and 8x 2.5" drives on a single back-plane 🤤. But alas, they don't offer it bare 😭. Here's to hoping that one day they change their mind or make something better to fill this dearth in our niche market segment. For a reasonably sized average 45L volume chassis, with a full back-plane for 10+ drives ... I would pay a premium! There are still some options in production by Fractal Design, Phanteks, and Rosewill that will support 10+ drives without breaking the bank only costing ~$200-$250 all in. Here are some as of January 2020: Fractal Design Fractal Design Vector Fractal Design Define R6 10x 3.5" drives (requires finding/purchasing 4 additional trays) Phanteks Phanteks Enthoo Pro Phanteks Enthoo Luxe 3x 5.25" + 6x 3.5" = 11x 3.5" drives (with 1 cage) Rosewill Rosewill Thor v2 (Might actually be out of production ... but currently available (in white) for $120 USD from Newegg) 6x 5.25" + 6x 3.5" = 16x 3.5" drives (with 2 cages) Also, as other's have reported, you can still find semi-reasonable prices on some second hand towers from the early-2010s. This is the option I am going with for my server. I just bought a NZXT H440, which is a hell of a nice case (IMHO), with lots of space for fans and breath-ability for keeping the drives cool. I plan on doing a simple mod to mount a total of 11x 3.5" drives in this platform. Actually, the last mounting location is odd, sitting on the bottom of the chassis, and I probably will not use it. But this will leave a good amount of "free space" which I was thinking about filling with a 6x 2.5" drive cage if I can find/tap a good mounting solution. I haven't built in it yet, so this is still TBD. But, for $80 shipped (after some hunting ... and sniping) ... DONE! -JesterEE

On the fringe of being related, here is a forum post I made on the Plex forum in 2018 cataloging some of my experiences while working with a RAM drive on a Windows server. Plex does some really strange stuff under the hood. TL;DR: Don't waste your time ... unless you have lots of RAM and nothing better to do with it (*looks down as to not make eye contact with anyone here* 😉). https://forums.plex.tv/t/plex-transcoder-ram-drive-experience

And they'll still blame you for "bad quality content" because they can't use the app right to increase the quality setting .... SMH 🤣. This is why I don't share my library (of Creative Commons content 🙃) with non-techies anymore 😋.

No problem. I do. I tried disabling it as suggested, but an getting the same result. I see you added debug logging, but I don't see an option to enable it. Here are outputs that I am receiving when restarting the Controlr server: System Log Jan 12 18:01:44 Tower ool www[17754]: /usr/local/emhttp/plugins/controlr/scripts/stop Jan 12 18:01:52 Tower ool www[19673]: /usr/local/emhttp/plugins/controlr/scripts/start Jan 12 18:01:52 Tower sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=root ; COMMAND=/usr/bin/bash -c /usr/local/emhttp/plugins/controlr/controlr -port 2378 -certdir '/boot/config/ssl/certs' /boot/logs/controlr.log I: 2020/01/12 18:01:52 app.go:57: controlr v2020.01.11b|2.18.1 starting ... I: 2020/01/12 18:01:52 app.go:65: No config file specified. Using app defaults ... I: 2020/01/12 18:01:52 app.go:214: cert: found Tower_unraid_bundle.pem I: 2020/01/12 18:01:52 core.go:73: starting service Core ... I: 2020/01/12 18:01:52 core.go:268: Created system sensor ... I: 2020/01/12 18:01:52 core.go:298: No ups detected ... It is worth noting that I am on a system that currently doesn't support monitoring of the CPU/motherboard/fans. The Linux kernel v4.19 on Unraid 6.8.0-Stable does not read my hardware. I am eagerly awaiting the next 6.9.0-rc (Soon™ 😭) so I can get on the Linux v5 kernel which I am hoping should fix it for the AMD Ryzen 3000/x570 chipset products. I know your software monitors this information, so while I do have the System Temp plugin installed, it is currently not monitoring any sensors. -JesterEE

For Firefox in particular, as a work around, I could use the built-in tinyproxy or shadowsocks in the docker to access the VPN. But, the overall networking pipework problem would remain for other apps that don't have a way of connecting to a proxy inside the app itself.

https://hub.docker.com/r/qmcgaw/private-internet-access/