News for hackers. Stuff that matters.
Re:AT&T updates firmware to block access to 1.1.1.1 by harshreality on Wednesday May 02, 2018 @09:33PM (#16982666)
In a cluster-in-a-box scenario, you could modify the OS's network scripts to have the cluster-specific private interface start after the general LAN interface is up. Check both 10/8 and 172.16/12 to see if they're used by the public interface, and use whichever one isn't for the cluster network.
Re:AT&T updates firmware to block access to 1.1.1.1 by derekp7 on Wednesday May 02, 2018 @11:06PM (#16983067)
That only works if the host is on the conflicting network. But if the conflict is a couple hops away, Docker won't detect it.