RusmanCool
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by RusmanCool
-
-
@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)
-
20 minutes ago, RusmanCool said:
Yeap, it was set to not check spun down disks.
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.
-
14 hours ago, Squid said:
FCP has an option to avoid spinning up disks
Yeap, it was set to not check spun down disks.
-
On 12/10/2020 at 8:10 PM, sivart said:
Interesting, I did not see this with beta35. My drives don't stay asleep with RC1. SMART queries shouldn't wake up the device.
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 -
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>
[6.9.0-rc2] Docker container br0 port mapping
-
-
-
-
-
in Prereleases
Posted
@showstopper, no, I have not. I have to use unraids's IP to map to nginx container, which in turn listens to 1443 port. I did setup DNS names for each of my containers, though each still points to my host unraid IP, but that allows a clean usage of nginx to direct calls to correct containers.