I had attempted to try a community docker app out, "matter-server" container by digiblur and it specifies having to have ipv6 enabled whether or not you actually use it.

 

So I enabled it, but quickly noticed that my SWAG container stopped working. This container I have on br0 so that I can assign an IP address within my local network range. 

 

I have found that the container will can no longer reach the internet to grab all the docker mods it is using and has some other errors as well due to not not being able to get to the internet. 

 

I have put the network back to IPv4 only and the issue persists. 

 

I can switch the container to any other network type be it bridge, host, or a custom docker network and it will work just fine. 

 

Any ideas?

 

 

Edited October 12, 20241 yr by adamfritzsche
Removing Images

I setup a new instance of unraid and the br0 and assigning an ip to the SWAG docker works as expected. So something somewhere is dorked up with my unraid instance. Is there a safe way to wipe my network settings replacing them with "clean" settings?

Stop vm and docker.  Rename /boot/config/network.cfg to something different.  Reboot and unRAID will build you a new network.cfg

This was my issue. The tailscale plugin. Did not associate it with this as I had TS running for weeks now without issue. Just so happens I have not restarted the docker service or unraid since then.