You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A very typical use-case is having services/containers that need to communicate with another on multiple hosts. Links & container naming already simplifies this process on a single machine. I see two possible ways to implement this feature over the network:
some kind of mechanism by which Docker instances can discover names and addresses of containers run by other Docker instances on different hosts and making those links available to local instances.
a command for manually injecting a remote container by giving the address of a remote Docker instance and a container name to link from the remote instance.
In both cases, the links should work the same as host-local links, i.e. tunnels should be created automatically when a link is established.
The text was updated successfully, but these errors were encountered:
There are a number of things planned for this - @crosbymichael has made skydock (using DNS for discovery), and then the ambassador pattern that has been documented is expected to be would into docker transparently so that the location of the linked container is abstracted.
if anyone's interested, we would love more help :)
A very typical use-case is having services/containers that need to communicate with another on multiple hosts. Links & container naming already simplifies this process on a single machine. I see two possible ways to implement this feature over the network:
In both cases, the links should work the same as host-local links, i.e. tunnels should be created automatically when a link is established.
The text was updated successfully, but these errors were encountered: