RusmanCool

Members
  • Posts

    11
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

RusmanCool's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Mobo: Asrock Rack x470d4u OS: UnRaid 6.9.0-rc2 Requirement: The mobo has two physical LANs. I'd like to access UnRaid GUI over one LAN physical port. And I'd like to have a single Docker Container to run off the second LAN over port 443. Unraid GUI should not be listening on the second LAN. Problem: Unraid GUI is listening on both LANs and thus I cannot assign/map host port 443 to to a docker container: Template configs Note: Due to this issue, I am still able to access UnRaid GUI from both static IPs on those two physical LANs. What I have done: Set Docker setting to use eth1 only: I have configured eth0 with Static IP = 192.168.0.8 and eth1 with Static IP = 192.168.0.9. I did not bond nor bridge them. See pic: My Routing Table(I have not made any changes to it directly):
  2. @Squid Thank you for the answer. I have a similar issue/requirement. Let me explain. I'd like each docker container to run on its own IP address. And its' internal whatever port to be mapped to host's port 443 for HTTPS communication on that unique IP address. I do still want to access Unraid GUI on its own IP on port 443 as well. I do not want to enter any port numbers in address bar. Example: Given Unraid GUI is running on IP=192.168.0.15 and listens on port 443 as I have added Let's Encrypt SSL cert manually And I have a docker container that I want to accesss from a different IP address ( like 192.168.0.20 )and on port 443(default for HTTPS) as well And internally, the container is listens to port 8888 The question: How do I set up that container to be on IP 192.168.0.20? And to map host port 443 onto container's 8888? I have tried: One: -p 192.168.0.20:443:8888 Network = eth0 Result: docker selects some port, ignores the IP and port I selected. The container can be accesses only from that selection: eth0 192.168.0.2:8888/TCP192.168.0.2:8888 Two: -p 192.168.0.20:443:8888 Network = host Result: docker selects some port, ignores the IP and port I selected. The container can be accesses only from that selection: eth0 192.168.0.2:8888/TCP192.168.0.2:8888 Three: Added 192.168.0.20 IP address on host as ip addr add 192.168.10.20/24 dev eth0 -p 192.168.0.20:443:8888 Network = bridge Result: Error starting userland proxy: listen tcp 192.168.0.20:443: bind: address already in use. Four: -p 192.168.0.30:443:8888 Network = bridge Result: Error starting userland proxy: listen tcp 192.168.0.30:443: bind: cannot assign requested address. I might miss on smth with respect to networking in docker, any advice how to achieve the given task is appreciated. Or if it cannot be done then a clear answer why is also important, so I move on to another option (I have several spare LAN ports not used but available to UnRaid, so I was considering to set dockers on their own LAN network throw a nginx proxy)
  3. I can confirm that after removing VM Backup plugin, the error is gone on unRaid v 6.9.0-rc2
  4. So, I had removed FCP plugin along with UD one. I have spun down all four disks, and after 16 mins they are still spun down, and there is only one extra ntpd log seen after them. So, that seems as those two plugins need an update to work properly with RC1 release.
  5. Yeap, it was set to not check spun down disks.
  6. Hi, I have just tried to spin down three WD RED and one Seagate drives. They had stayed spun down for two mins. However, I did see them spun up. However, there is a log msg that Fix Comon Problem plugin had found a warning, and right after that disks had spun up. See below: Dec 14 03:27:02 HomeNAS emhttpd: spinning down /dev/sdd Dec 14 03:27:02 HomeNAS emhttpd: spinning down /dev/sde Dec 14 03:27:02 HomeNAS emhttpd: spinning down /dev/sdb Dec 14 03:27:02 HomeNAS emhttpd: spinning down /dev/sdc Dec 14 03:29:00 HomeNAS root: Fix Common Problems Version 2020.12.05 Dec 14 03:29:00 HomeNAS root: Fix Common Problems: Warning: Plugin Update Check not enabled ** Ignored Dec 14 03:29:00 HomeNAS root: Fix Common Problems: Warning: Docker Update Check not enabled ** Ignored Dec 14 03:29:01 HomeNAS emhttpd: read SMART /dev/sde Dec 14 03:29:05 HomeNAS emhttpd: read SMART /dev/sdd Dec 14 03:29:05 HomeNAS emhttpd: read SMART /dev/sdb Dec 14 03:29:05 HomeNAS emhttpd: read SMART /dev/sdc
  7. Hello, I was able to configure my Ryzen 3950x CPU for Windows 10 VM with "host-passthrough". So, now Win sees cpu correctly. Below are my configs for VM settings xml file: <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu>
  8. I have vDisk as VirtIO in Windows 10 VM. I have set its capacity to 2TB and its current allocation is 39GB. So, the problem I see is when I copy some data in amount about or above 1.5GB onto it, data starts writing onto it with a good speed of above 100MB/s; however, after a short while and before all data is written, the disk stops writing ANY data but its Active Time is at 100% at that time. After about 15-25 seconds, data continues to write. But the same keeps happening over-and-over again until all data is copied! What is wrong? <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/Media/Videos/someDiskName.img' index='2'/> <backingStore/> <target dev='hde' bus='virtio'/> <alias name='virtio-disk4'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </disk>
  9. Any reply from UNRAID tech support as I see it after every other one search now?
  10. 128 GB DDR4 ECC with Ryzen 3950x CPU and Asus Pro WS X570-ACE mobo.
  11. Great job..., would you be so kind to share this info?...