Hi All,

Currently setup:

running unraid 7.0.1 and my docker network is set for br0 which has eth0 (10G pci card) attached and my docker network is currently setup as ipvlan. I have eth1 (1G on motherboard) available for this activity. This works fine for my use up to my current situation.

Target approach:

I'm attempting to setup a headless steam install to be able to share my Arc b580 with other dockers compared to allocating it to a VM or dockers - obviously can't do both and currently have dockers utilizing the GPU so the pass through appears to work so far. I've tried the steam headless docker but that can't utilize the gpu, its detected but vainfo does not open it so I've moved to the linuxserver.io image of steamos. That appears to detect my gpu properly although when ran in host mode it breaks my unraid network settings preventing community applications from connecting out. Per the linuxserver details it is recommended to use either host or macvlan for this docker yet host mode breaks my setup and looking to avoid trying to setup all dockers on macvlan and break it all.

Question:

Is there a method to utilize the second NIC for a "host" mode of operations without impacting the core unraid functionality and still be accessible on the same subnet? Was thinking of assigning the NIC to only this docker and using a dedicated IP within my 192.168 subnet beyond the unraid IP.

I may be looking at this in the wrong way but trying to determine the best method forward for this situation so any assistance is greatly appreciated.

Also wasn't 100% on where to post but please feel free to move as needed.

Review:

??? host give all interfaces that unriad has to the docker...

You would need to vfio and pass this to the docker via devices. use a bridge or vlan to separate and use traffic.

the linux server docker should be ran in a docker bridge mode...
https://hub.docker.com/r/linuxserver/steamos

Edited June 22, 20251 yr by bmartino1
data - typo

otherwise make a docker network... I can't guarantee ip routes to not use the eth0 10 GB interface over the eth1 1 GB interface if on the same subnet... not enouth info to further assist...

You can absolutely dedicate eth1 to a single container without disrupting unRAID’s core network. The best approach: create a macvlan or ipvlan Docker network on eth1, then attach only that container to it. Here’s how

Create a macvlan network on eth1

docker network create -d macvlan \

--subnet=192.168.1.0/24 \

--gateway=192.168.1.1 \

-o parent=eth1 \

steamnet

I Prefer macvlan... heres ipvlan

docker network create -d ipvlan \

--subnet=192.168.1.0/24 \

--gateway=192.168.1.1 \

-o parent=eth1 \

steamnet-ipv

This isolates traffic: containers in steamnet send and receive only via eth1

see: https://forums.docker.com/t/using-a-second-nic-exclusively-for-docker-services/127180

Launch the Steam container on that network

docker run -d \

--name steamos \

--network steamnet \

--ip 192.168.1.80 \

linuxserver/steamos

*You would edit the docker tempate and selct steamnet in the netowrk dropdown...

-This gives the container a dedicated IP on your main subnet, shared with unRAID's interface on eth0, but routed separately thanks to macvlan isolation.

Why this works

• Docker creates a virtual NIC tied to eth1 inside the container.

• The container’s network is entirely isolated from br0/eth0 paths .

• Other containers and unRAID services stay unaffected.

Note: Don’t use --network host!

• Host mode exposes all host interfaces to the container (including eth0), which you experienced breaks core services

Greatly appreciate the above breakdown. I'll give it an attempt shortly when time permits.