- Annoyance
I don't know if it's really a bug related to Unraid or just a speciality in the way Unraid handles docker.
For easier management and a consistent Gui across multiple platforms im using Portainer to manage my docker containers.
I came across the problem, that in some cases redeploying a docker-stack/docker-compose can lock me out of Unraid Web-Gui and ssh while managing the server from a VPN network. The IP is not even pingable. The Unraid server is still reachable from within ist Local network. There is no misconfiguration in the Firewall or VPN access (Unifi Dream machine Pro in my case).
As far as my research gotten, docker compose creates a separate network as it is supposed to do. But instead of creating a 172.*.*.*/16 network compose is creating 192.168.*.*/255.255.240.0 Network. This is in some cases conflicting with the VPN Network or other local VLAN ip ranges. As Docker is generating its own iptables rules always on top of others, there is obviously no access from all ip ranges conflicting with a docker-compose network. As the intention of using docker compose is, to not really care about the exact ip range a backend bridge network is using, and Unraid is the only platform I've send this problem its maybe problem related to Unraids way of handling docker or networks.
In my research regarding this behaviour I've seen some posts by others with similar problems which lead to either no solution or the solution of stopping the docker service at all.