3 ms·
I'm not sure I even understand the problem that weave and Docker bridging/NAT solves for real world cases. IP allocation for containers isn't a problem for mos
by otterley 12y ago
I'm not sure I even understand the problem that weave and Docker bridging/NAT solves for real world cases. IP allocation for containers isn't a problem for most networks, is it? Certainly AWS can give you up to 8 IPs per instance, and every datacenter I've ever worked in can give you even more, if you ask. All you have to do is spin up additional virtual NICs with virtual MACs and use DHCP to assign IP addresses to them.
Or is there something fundamental that I don't understand? Please edify me.
- wmf 12y agoDocker was designed to be very easy to get started on your laptop with one IP address and it looks like some people are getting stuck in that model. I agree that if you are running on AWS VPC or some other overlay you should just use VPC for container networking. You shouldn't overlay your overlay. But there isn't any tooling that I know of to do that.
- otterley 12y agoEveryone I know who runs Docker runs it in a virtual machine manager that has a built-in DHCP server and provide multiple virtual interfaces to the virtual machine. Certainly both VirtualBox and VMWare do. Even if one runs a Docker bridge in his development VM, that doesn't one must do so in production as well. Are we in this mess because production engineers don't understand networking?
- bmurphy1976 12y agoWe're in this mess because cloud providers don't give you all the functionality you need to solve things properly. It's only a matter of time before they do, until then...