lrussell887

Hey everyone, I'm looking to set up a custom Docker network with a custom subnet specifically for use with Tailscale on my Unraid server. Currently, I'm using the default br0 ipvlan docker network in Unraid, which has the br0 interface as its parent. This lets me assign a LAN IP directly to a Docker container, which is important for things like Pi-hole. I can make LAN IPs accessible over Tailscale using the Tailscale plugin by subnet routing 192.168.1.0/24, or by individually forwarding IPs, such as 192.168.1.11/32. I also had to enable "Host access to custom networks" in the Docker settings. However, what I'd really like is to create a custom subnet, like 192.168.123.0/24. This would allow me to assign an IP address to a container, such as 192.168.123.2, and then use subnet forwarding in Tailscale to advertise the route 192.168.123.0/24 making it available through my tailnet. This approach becomes particularly useful when I take my laptop with Tailscale and connect it to another network where, for instance, 192.168.1.11 may already be in use locally. I attempted to create a custom network with the following: `docker network create -d ipvlan --subnet=192.168.123.0/24 --gateway=192.168.123.1 -o ipvlan_mode=l3 -o parent=br0 tsbr0` However this didn’t work since the parent br0 interface is already assigned to the br0 docker network. I still need Docker containers assigned to this custom subnet to have internet access as well, which as I understand would require routing, hence `ipvlan_mode=l3`. I'm uncertain how to tie all of these elements together though, or if there's a better approach to achieving my goal. I'm currently using the latest Unraid version (6.12.8). Any guidance or suggestions on how to create this would be greatly appreciated.

Yes, I can confirm switching to that repository works, not sure how I missed it on docker hub before. Thanks!

Is this still being updated? The last update looks to have been about a year and a half ago, making the Alpine version it's based on rather old now. It's using 3.12 when current is 3.19. I'd like to use this for my off-site backup but am a bit apprehensive due to this. There looks to be someone maintaining a fork with a bot that updates the Alpine version which the EEA doesn't appear to have done for 4 years. https://github.com/mtandersson/eea.docker.rsync