New version of Eddie screws up Docker containers

[Woudy1945 0]

I recently upgraded to the latest version of Eddie on a Debian system and immediately was unable to access several Docker containers I had no issues with in the previous version. I don't know if this is a bug or a Docker skill issue, as I'm still a novice with Docker.

For several months I've had a successful Docker set up with multiple containers that use containerized databases. Everything has worked well. As soon as I installed the latest version of Eddie and connected it, the Docker containers could not connect to their own databases any more. Once I disconnected Eddie, the containers went back to working as intended. I tested this using both the Wireguard and OpenVPN protocols inside Eddie, with OpenVPN tested on both UDP and TCP. As soon as I downgraded back to the previous version of Eddie, everything functioned as it had before, no issues with the Docker containers using either protocol.

I run a Debian system with the latest version of KDE. In the new version of Eddie, when connected, there is an indicator in my system tray about Eddie being connected to Wireguard. That indicator is not present when connected using the old version of Eddie. There must be something different about the way the two versions are interacting with the system, and maybe that's affecting the Docker containers. I'm not a developer and my networking skills are not fantastic, I'm unable to get any further into this mystery.

For now, I have downgraded to the old version of Eddie, which works perfectly as expected.