Quote

With only a single NIC, and no VLAN support on your network, it is impossible for the host unRAID to talk to the containers and vice versa; the macvlan driver specifically prohibits this. This situation prevents a reverse proxy docker from proxying unRAID, but will work with all other containers on the new docker network.

 

This is my problem, I NEED to run netdata docker on the host network to be able to fully see host stats, but I need to run my nginx and all other dockers on br0 macvlan, is there ANY way to let nginx proxy/talk to netdata (eth0 to br0)?

 

This is something I've found online but I get device busy when trying to implement even with everything unplugged.
 

Quote

curl: (7) Failed connect to 10.12.0.117:80; No route to host

 

The host is unable to communicate with macvlan devices via the primary interface. You can create another macvlan interface on the host, give it an address on the appropriate network, and then set up routes to your containers via that interface:

 

# ip link add em1p1 link em1 type macvlan mode bridge

# ip addr add 10.12.6.144/21 dev em1p1

# ip route add 10.12.0.117 dev em1p1

 

Any ideas?

I have the same issue.
Adding a route does not cut it, apparently.
I've tried everything in this post.