3 ms·
This is an interesting idea. It might be useful to have a high level architecture diagram to illustrate what is happening between the containers. A couple issu
by WestCoastJustin 13y ago
This is an interesting idea. It might be useful to have a high level architecture diagram to illustrate what is happening between the containers.
A couple issues:
1. Using localhost seems like a bad idea (I have the expectation that traffic is local to the instance if using localhost). 2. Managing more then a couple instances of this will be unmaintainable if done manually. There will need to be some controller logic happening.
Maybe I am missing something, but why not add a second dedicated virtual ethernet adapter where all your containers can talk (works across containers and across servers)? This is traditionally how you would handle something like this. We have dedicated nonroutable reserved address space configured to handle all this internal datacenter traffic.
- nl 13y agoThat certainly seems preferable, but I guess "localhost" has the advantage of always being there (which is what you want for a service discovery bootstrap mechanism) I believe Docker is guaranteed to have the docker0 interface[1] available, but perhaps the proposed mechanism doesn't want to tie itself to Docker so tightly? [1] http://docs.docker.io/en/latest/use/networking/ http://docs.docker.io/en/latest/use/networking/
- jpetazzo 13y agoActually, Docker doesn't always have docker0; you can configure it to use a different bridge. On my setup, for instance, I use br0 and share the same bridge for containers and VMs.
- nl 13y agoYeah, ok - Docker defaults to having docker0. I guess this conversation kinda encapsulates the problem..