-
Derek started following Realtek RTL8156 drivers and Issue Connected to My-SQL-Server Docker Container from SSMS
-
Issue Connected to My-SQL-Server Docker Container from SSMS
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!
-
Realtek RTL8156 drivers
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?
-
Realtek RTL8156 drivers
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.
-
MSSQL Docker on UnRaid
This is great, thank you!
-
Derek started following [6.6.0] sftp transfer issues
-
Derek started following Losing All Network Connectivity 6.6.0
-
-
[6.6.1] docker stats command for cpu load and memory load running almost constantly
The following command within 6.6.0 (and now confirmed in 6.6.1) seems to be constantly running: docker stats --no-stream --format={{.Container}} {{.CPUPerc}} {{.MemPerc}} USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 8955 13.0 0.3 40972 26028 ? Sl 09:55 0:00 docker stats --no-stream --format={{.Container}} {{.CPUPerc}} {{.MemPerc}} I am running unRAID on a low power consumption based system backed by an Intel Celeron J3455 processor so I don't always have spare cycles -- this command finishes after approximately 0.6 seconds and starts almost immediately again 24/7 (based on what I can see with the PID constantly changing) and it is generating a little bit of a load on my load average outputs. It nearly always consumes 10 to 13% of my CPU while running. To remediate this, I would expect that this command should only run only when the docker page is being viewed on the Web UI, and ideally only if the advanced view is turned on as it is really only for informational needs.
Derek
Members
-
Joined
-
Last visited