Jump to content

Docker containers separate NIC from unRAID

3 posts in this topic Last Reply

Recommended Posts

When I move files across the network and fully saturate my eth0 connection the docker container network performance suffers. I'd have a 4x NIC card I'd like to put the docker traffic on. From what I've read this isn't possible if both of the NICs use the same gateway. I only have one subnet on my network though.


What is a good approach for separating unRAID traffic from docker?

Share this post

Link to post

I too would like to do this. I have tried in the past with my quad nic and the outbound traffic from docker always goes out eth0 (my onboard nic) regardless.

Share this post

Link to post

Went down this rabbit hole a bit. Not sure if this will help you.


On mine, I have a 10GB as my "main" link eth0. Then eth3 is a 1GB nic. I attached the 1GB nic to an extra port on my router, and made a new interface and allowed the two subnets to talk to one another, and I plan on separating where each subnets WAN traffic goes. But, a by-product is I can use either br0 or br3 for dockers for them to go to either nic.


Either that, or just bond all your available bandwidth and call it a day.

Share this post

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.