https://bugs.winehq.org/show_bug.cgi?id=56790
--- Comment #7 from contact@msteinbusch.nl --- (In reply to Hans Leidekker from comment #6)
Chances are that this is fixed with 72f11610cafb018fde8c56e05003c2448a314490. Can you test?
I can confirm this somewhat fixed the issue.
At one point, the server was binding itself to a Docker bridge ()172.22.x.x interface for some reason. However, after disabling Docker and testing again, it correctly bound to the intended interface, such as 192.2.1.200. This wasn’t possible before! I cleaned up unused docker networks rebooted with docker still enabled and it still binded to the correct interface.
In my Docker setup, I only have two interfaces, so I’m confident it will work properly now. Unfortunately, I wasn’t able to test it within my Docker containers since I need to wait for the fix to become available in the ArchLinux repository.
I'm exited to see this fixed!