5 ms·

Thanks! Let us know what you want covered.

• olavgg 12y ago
  The one thing I've spent most time getting right with Docker is networking. It's so different from FreeBSD Jails. I believe a guide with how to setup a dns container with a dns slave container and get other Docker containers to use the dns containers could be a good introduction to how Docker networking actually work.
  • aidanhs 12y ago
    Networking with Docker is a pretty hefty topic. One of the interesting things talked about in the book in this area is skydock[1], which provides automatic dns registration inside docker when you start your containers. We've found it very handy for simulating a network of real machines! [1] https://github.com/crosbymichael/skydock https://github.com/crosbymichael/skydock
  • bboreham 12y ago
    You may also like to look at Weave[1], which includes an open-source network for Docker and DNS service to find other containers. [1]: http://weave.works/ http://weave.works/ Note: I work on Weave.
• iends 12y ago
  I work at a company whose main product is a small application using SOA of about 15 services. Managing these 15 services in development is getting to be a nightmare. I would love to know if docker is the right solution to manage these services. Spinning up 15 VMs on a MBP is not really feasible...
  • zwischenzug 12y ago
    It sounds like a very apt use case, unless you need the VM representation for some reason. 15 separate services is no problem for Docker. Hundreds - if not thousands - are quite possible.