4 ms·

Hi shykes, Well, first of all, thanks for Docker, it is a great product, love using it! My only criticism is: I find it scary and kind of shortsighted that d

by buster 12y ago

Hi shykes, Well, first of all, thanks for Docker, it is a great product, love using it! My only criticism is: I find it scary and kind of shortsighted that docker (and even more so rocket) seem to neglect basic networking features. From what i can tell everything is based on the approach that you write your webapp with docker in mind, but i for one, would like to use my legacy applications with docker and i would like to write applications with full networking in my control. I really, really don't want docker to choose some IP for me. And i really really don't want my apps to talk over some random ports. I want control. So far everything is still based on some random interfaces and ports that are passed around.

MichaelGG 12y ago
Bingo! We looked at Docker for VoIP a while ago and it didn't appear like it was a good fit for such applications. To be fair, Azure had the same odd-sighted flaw, although they have a weak workaround with public IPs now.
teabee89 12y ago
(disclaimer: I'm one of the Docker maintainers) We hear you and we already started working on addressing just that. The goal is to define a networking interface (a set of functions) that networking plugins would satisfy. Again: "batteries included but removable". There's a lot of work to be done and details to be figured out, but I can assure you that networking is not left out, and is going in the right direction as well. We will send out a proposal on Github as soon as we can. Stay tuned!
- shykes 12y ago
  FYI today we had a design session on this topic with several members of the ecosystem (Weave, ClusterHQ, Socketplane, Tutum, VMWare) during Dockercon. As soon as there's something worthy of a proposal, we'll open it up for comment on the repo. I'm pretty excited about this.