Docker Containter NIC Isolation


Xuvin

2 posts in this topic Last Reply

Recommended Posts

Hey :D

 

I hope this is the right forum thread for my question ;)

 

I would like to run a PBX software in a Docker Container and my IT guy recommended me to use a dedicated ethernet port, because it would be a better experience in relation to voice quality, etc.

 

However, I am using the Supermicro - X11SSH-CTF, which has two ethernet ports, so I am asking myself how can I isolate or dedicate one of those ports to one specific Docker Container ?

 

Hope you can help me out 😊

 

Edit:

Or is it as easy as just selecting one eth0 for one container and eth1 for all the others ?

Will unraid (webgui, etc) be operational on both interfaces instead of one ?

Edited by Xuvin
New Idea
Link to post

Disable the default docker custom network on eth0 (it will be for your LAN subnet)

Create a new custom docker network on eth1 (this wil be for your LAN subnet and assign a DHCP pool that does not conflict with any reserved addresses on your LAN or the DHCP pool managed by your LAN DHCP server, typically the router. - docker custom networks have "DHCP" for containers that do not attempt to check or verify with the LAN)

Assign the container to this network (actually if you have any other containers that need an IP on your LAN, they all need to be migrated)

 

references:

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.

Guest
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.