I have searched the internet and no one seems to have the same issue.  I hope I'm wrong and someone can steer me to where others have gone before.

 

My docker containers that are on the custom br0 network do not get assigned an IP from my router.  These are the ONLY things on my network that are not automatically assigned.

Unraid gets an IP just fine.

I have Home Assistant running in a VM - it gets an ip.

I have SWAG and PiHole setup on br0.  Neither gets an IP assigned from my router.  Both are reachable by ping through their IP addresses set in the container themselves.

 

Docker settings:

Docker custom network type:
    ipvlan

Host access to custom networks:
    Enabled

 

Network settings:

Enable Bridging:

    Yes

If you want your containers to have a different address than your host you can either assign it in the optional spot (if already built in) or got to the container console and run ifconfig.  You should find the Mac address in there that you can use to configure your DHCP server.

If you attach diagnostics some more info can likely be found by some of the pros that hang out on these forums.

Here are my diagnostics if this helps.  I checked out ifconfig but did not see anything listed for the ip address that shows in the Docker tab for my container.

tower-diagnostics-20250115-2142.zip

If you console into the container and do ifconfig there, you will see the mac address that unRAID gave it.  With that mac, you should be able to configure your DHCP server to assign your chosen IP to it (the mac).

The easiest is to assign your IP address manually though. 

 

Ahh, I'm sorry that I did not make that clear.  That was already filled out.  I am able to reach my pihole through that IP.  But neither my pihole or my swag container are getting IP leases from my router.

I even added the lease using the container MAC but nothing.

In the image it shows network type is custom: bond0

Can you change that to read something more like custom br0 - eth0?  

I can change it back.

 

Since I posted about this, I changed the docker custom network type to macvlan since I saw that they fixed it.  That changed my network to bond0.  But I didn't get an IP assigned regardless.  I'm now switching back.

My last idea is to change DNS IP to 1.1.1.1 or 9.9.9.9 or something.  Just give it an option that is not a recursive/unbound DNS like what you may be using.  

For my understanding, docker container won't got IP from outside (unraid) DHCP.

7 hours ago, Vr2Io said:

For my understanding, docker container won't got IP from outside (unraid) DHCP.

only for bridge mode if set to custom it should grab from the router.

 

Unless you setup a dchp pool for ipvlan/macvlan... then the docker network can use from a set ip range. Then it will still ask the router and use the first IP in the IP range.

It is better to static assign a ip address to a docker.

On 1/15/2025 at 10:04 AM, Eksistenze said:

I have searched the internet and no one seems to have the same issue.  I hope I'm wrong and someone can steer me to where others have gone before.

 

My docker containers that are on the custom br0 network do not get assigned an IP from my router.  These are the ONLY things on my network that are not automatically assigned.

Unraid gets an IP just fine.

I have Home Assistant running in a VM - it gets an ip.

I have SWAG and PiHole setup on br0.  Neither gets an IP assigned from my router.  Both are reachable by ping through their IP addresses set in the container themselves.

 

Docker settings:

Docker custom network type:
    ipvlan

Host access to custom networks:
    Enabled

 

Network settings:

Enable Bridging:

    Yes

Id have you review 

 

 

To gain a better understanding of unraids networking and docker networking.