I upgraded docker on my laptop (which was previously running the same version as my desktop) and its not having the same issue. I've been able to rule out the docker update as the root cause. What are some steps I can do to try to troubleshoot what is going wrong in docker to prevent access outside of localhost? I was able to confirm its not the DNS A record because I'm able to use the RDP ports I have mapped for my router, and when I test on another machine in the same network, it can't access the services via the internal IP (but it can RDP).Īnyone have any idea what could have changed to break this? I've already updated all my docker images and even rebuilt my VPN container (before I realized its a networking issue). Usually I have a poke through for a couple of the services in my router (namely wordpress/joomla which is on the bridge) and they work outside of my local network, but none of them are working anymore. I ran the docker update for windows and now docker spools up without any errors or issues, however none of the services work outside of the machine running docker. The strangest thing happened today though. the first network just bridges the docker instance to the local machine, the second network is a docker VPN container that I use for the other media services (an earlier version of what I am working on can be found here: ) I have everything networked into two different docker networks. I have been running a media cluster for sometime without any issues.

Ideally you would need a 3rd node to reach quorum and prevent split brain scenarios, but you get the idea right?

The nodes could monitor each other to withdraw the static routes if the other fails.

When NodeB starts it automatically makes an API call to create a route for 10.2.1.1/32 and points to itself with preference 1.

When NodeA starts it automatically makes an API call to create a route for 10.2.1.1/32 and points to itself with preference 2.

Start a heartbeat send/receive between them.

Create a loopback interface on both VMs and set the same IP address for both like (10.2.1.1/32).See this link on GCP about floating IPs and their implementation. I have not personally done this on Digital Ocean, but I assume that you can call the cloud's proprietary API to do this functionality if you would like to go this route. Even if ARP worked,the IP allocation process for these IPs (often called “floating IPs”) would not integrate with the virtual network in a standard way, so your OS can't just 'grab' the IP using ARP and route the packets to itself. Most of the L2 failover protocols do break for that reason.

GCP etc.) ARP is emulated by the virtual network layer, meaning that only IPs assigned to VMs by the cloud platform can be resolved.

Udp2raw ipk download