10GbE on specific docker container

[kayjay010101]

I'm trying to get a docker container, specifically the lancache-bundle container, to run off my 10GbE peer-to-peer NIC. I tried to set it up like this: 

On a custom network that I created with the subnet 192.168.11.0/24. However, once I create it I get this error:

If I try doing it on "Bridge" or "Host" it will only get the local IP of the 1Gb NIC that Unraid runs on. I'm at my wits end on this. Could anyone help me with this so that I can finally utilise my SSD's speed for Steam-caching?

[Xaero]

Why not run Unraid on that 10gbe nic? Then all of the containers can share that 10gbe bandwidth, lancache included. Significantly reduces the level of complexity, as well. Also the error you are getting right now is due to trying to bind 0.0.0.0:80 which is already in use by Unraid in this case. You should be able to use the container IP (192.168.11.150) instead of 0.0.0.0 but I'm not sure how to do that with this container.

[kayjay010101]

8 minutes ago, Xaero said:

Why not run Unraid on that 10gbe nic? Then all of the containers can share that 10gbe bandwidth, lancache included. Significantly reduces the level of complexity, as well. Also the error you are getting right now is due to trying to bind 0.0.0.0:80 which is already in use by Unraid in this case. You should be able to use the container IP (192.168.11.150) instead of 0.0.0.0 but I'm not sure how to do that with this container.

The 10Gb NIC goes right to my computer, so it wouldn't have access to the internet, right? So not really an option?

These are the only settings that pertain to IP adresses in the container, they're all set to the 192.168.11.x address:

There are also more port settings under "More settings...", but these specifically say NOT to change:

 

 

 

 

Edited March 13, 2020 by kayjay010101

[Xaero]

55 minutes ago, kayjay010101 said:

The 10Gb NIC goes right to my computer, so it wouldn't have access to the internet, right? So not really an option?

These are the only settings that pertain to IP adresses in the container, they're all set to the 192.168.11.x address:

There are also more port settings under "More settings...", but these specifically say NOT to change:

 

 

 

 

Set the LANCACHE_IP to 192.168.11.150 AND DNS_BIND_IP to 192.168.11.150. Has to be the same as the Container IP.
With it set to the Unraid IP it is trying to bind 0.0.0.0:80 which is going to try and bind 192.168.11.149:80 which is already in use by the Unraid WebUI. Can't have to services on one port so you get the error and it dies.

Edited March 13, 2020 by Xaero

[kayjay010101]

1 hour ago, Xaero said:

Set the LANCACHE_IP to 192.168.11.150 AND DNS_BIND_IP to 192.168.11.150. Has to be the same as the Container IP.
With it set to the Unraid IP it is trying to bind 0.0.0.0:80 which is going to try and bind 192.168.11.149:80 which is already in use by the Unraid WebUI. Can't have to services on one port so you get the error and it dies.

It actually is set to 192.168.11.150, I changed it for some reason prior to taking the screenshot but I changed it back afterwards. The Unraid UI is running on 10.0.0.41 anyhow

Edited March 13, 2020 by kayjay010101