Skip to main content unRAID Routing Docker Containers (Bridge & br0) : r/unRAID
r/unRAID icon
Go to unRAID
•

unRAID Routing Docker Containers (Bridge & br0)

Help

Good morning everyone!

I'm fairly new to unRAID (running on a trial) but it seems to be really solid. As I'm getting older (30 :D) I'm getting tired of tinkering and just want something that will work with minimal effort.

I'm hoping I found that in unRAID. That being said, I have a few docker containers that I run as br0 on my local LAN. My main network is 192.168.1.0/24. I've assigned a few docker containers under br0 192.168.1.31. I can access these IPs from internal devices, however unRAID itself can't reach these.

This is causing an issue with Nginx Proxy Manager, running as bridge mode not as a br0 network, it can't communicate to the containers on the LAN network.

Any ideas?

r/unRAID - Left, Windows PC able to ping br0 container @ 192.168.1.31. Right, unRAID unable to ping br0 device @ 192.168.1.31.
Left, Windows PC able to ping br0 container @ 192.168.1.31. Right, unRAID unable to ping br0 device @ 192.168.1.31.
Slash review times, eliminate bugs, and get valuable insights into your projects and code.
  • Slash review times, eliminate bugs, and get valuable insights into your projects and code.
  • Slash review times, eliminate bugs, and get valuable insights into your projects and code.
  • Slash review times, eliminate bugs, and get valuable insights into your projects and code.
  • Sort by:
    Best
    Open comment sort options

    Use bridge for your dockers. The lease boy one I use with host is Plex.

    This is intentional for macvlan networks (what br0 is). By default the host will not be able to connect with any container running on br0 and visa versa. You should ideally run everything you possibly can in bridge mode (or even better in a custom bridge network especially if you're using a reverse proxy, lets you just use host names instead of IPs). That being said if you have a legitimate use for using a macvlan network, you can go into docker settings and change the setting "Host access to custom networks" to enabled

    More replies