6.12.rc8 but this has been a thing for me since 6.9.xxx.
Question:
Docker custom network not showing as an option (one that is actually tied to a nic)
Custom Docker network br.2 (eth2) will not show up for my docker containers. I have it checkmarked to be available to the docker services in docker settings. I have host communications enabled.
I have the motherboard NIC used as the unraid connection.
I have a 2x2.5gb nic in a pcie slot. one port is a straight connection from my server to my windows pc. the other, eth2, I am trying to use for a camera setup. I have interface eth2 bridged to itself. I have tried it bridged to itself, bonded to itself, bonding and bridging disabled.
I was able to get it to pop up, briefly, after I realized my IOMMU groups werent available due to a bios update I did. I reenabled Intel Virtual stuff in the bios, and when I rebooted(after rebuilding my docker image bc enabling that corrupted my docker image) the network was available. I needed to reboot before I could implement it with the docker I wanted, and then it disappeared never to be seen again.
I have cheated this, but it doesn't work as I want. I bridged eth2 to itself, and ran:
docker network create \
--driver=bridge \
--subnet=172.17.0.0/24 \
--gateway=172.17.0.1 \
br2
This made the docker network available, and even brought up the name I had named it. but what it did was connect as if it was br0 and not br2.
Any help, or if you need any more information, that would be great and I will provide it if I can.