Derek

In Sql server management studio, make sure for a server name you use the unraid server name or IP address. You can also append ,1433 on the end of the server name to give it an extra hint to use TCP/IP to connect. For example, connecting to an ip of 192.168.0.200 you would specify: 192.168.0.200,1433 you also need to select SQL server authentication from the authentication dropdown (so that the username/password boxes become writable) username is: sa password is: <whatever you configured on the docker config page> Good luck!

Tom, it looks like there's an updated linux driver published 10/19/2020 on the page you linked -- maybe they've made some changes that will help?

Count me in too, I'm also out of PCI-E slots until I do a hardware refresh -- ESXi just added support via their USB Network Fling for the RTL8156 chipset so I'm a little sad it's not working in Unraid yet. I have not attempted to build a custom Unraid kernel, but I'm guessing that would likely be the other way to get this working as the RTL8156 driver is a kernel module.

This is great, thank you!

That is amazing! Thank you! Can I send you a beer, coffee, etc? 😃

No problem! I created a feature request here. Thanks!

I'd like to see the Unraid GUI only run the "docker stats" collection command when the docker stats are being actively viewed in advanced view mode within the web UI. This command is expensive, power consuming, and serves no purpose if the stats are not actively viewed on the docker page. On a lower end system like my Intel Celeron J3455, it consumes 10-13% of cpu almost constantly 24/7 (there is only about a 400ms break between the command starting/finishing where the CPU can idle). See this bug thread for more detail:

I agree, I am running plex and some other dockers. Raw CPU horsepower doesn't really concern me here, it just seems like this is an expensive command on any level of processing power if it's strictly for a display that is rarely viewed. Just surfing through some of the docker bug reports on the stats command, they seem to be well aware that it is an expensive command to run and do not have a fix in place yet. e.g.: https://github.com/docker/for-linux/issues/190 For example, my plex docker on unraid with hardware Intel Quick Sync transcoding of 1080p or 4k is able to easily serve my 2 endpoints at home without consuming much more than a constant 5-10% of CPU. Other containers don't consume much either -- as is the case similar to full blown VMs, having available RAM seems to be more important in most cases. I do run VMWare ESXi on a Xeon based server for most of my other needs that require more power, but I wanted to keep plex on my Unraid server because my Xeon does not have Intel Quick Sync. I'll work on submitting a feature request.

I can also confirm this behavior has not changed in any of the newer versions of Unraid but I did report it several months ago and to date, 6.6.6 also exhibits this behavior. I would still consider this a bug as Unraid is polling for these stats 24/7 and wasting CPU cycles on a relatively expensive command when it appears that it is not used for anything other than an informational UI display (which is not even visible unless the Advanced docker UI display is open).