You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw this in #56 - "There is an issue with the Consul Docker image, where you must run the container using --net="host". otherwise, communication is unstable."
Is it possible to provide any detail on whether this is still true? Haven't seen this at all, but keen to find out more
The text was updated successfully, but these errors were encountered:
I would believe that this was not only AWS issue - but more general docker networking problem related to mac address changing and ARP table timeouts in the network. Might be described here in more detail: moby/moby#4581
Running progrium/consul docker on AWS.
I saw this in #56 - "There is an issue with the Consul Docker image, where you must run the container using --net="host". otherwise, communication is unstable."
Is it possible to provide any detail on whether this is still true? Haven't seen this at all, but keen to find out more
The text was updated successfully, but these errors were encountered: