brokenworld

Hi, I have enabled "Host access to custom networks" in Docker settings which normally creates the shim-br0 macvlan bridge on boot. But, if the physical network link is down (e.g. cable unplugged), the shim-br0 is not created on boot, causing routing problems between the containers (e.g. when using Nginx Proxy Manager reverse proxy logs report "No route to host") I would understand this issue if I my Unraid would use DHCP, but my Unraid's network address, DNS and gateway is configured with STATIC addresses. To fix, I would suggest to not start docker service on boot until physical network link is up (e.g. network cable is plugged in). Any suggestions for a work-around in the meantime ? Thanks for any help. Edit: I found some code in the forum to manually create the shim-br0 bridge, but I am reluctant to use it because of the hard-coded IP ranges and implementation via cron. A more elegant approach to this problem would be nice. ip link add shim-br0 link br0 type macvlan mode bridge ip link set shim-br0 up ip route add 192.168.1.0/25 dev shim-br0 ip route add 192.168.1.128/25 dev shim-br0

@Alacard thanks for your effort! I am coming from a QNAP as well and Im quite surprised that this per-user "Home"-feature is neither implemented nor requested a lot by the community. Does your solution/script still work with latest Unraid 6.9.2 ?