when running an app in CF based on a docker image, the service discovery
mechanism is expected to be either through bound services which are
expressed as environment variables, or using DNS to reach another app via
route or an external hosted network service. user provided service
instances are a straight-forward way to express which postgres and rabbit
information to bind to an app. the service bindings are capable of
expressing more than just where the host is located, but also credentials,
ports, and other information relating to the service instance.

the cf diego networking team has service discovery on it's list of items,
but docker links assume certain things about service discovery that likely
will not work in other runtimes like cloud foundry or kubernetes.

On Tue, Feb 23, 2016 at 12:29 AM, Kayode Odeyemi <dreyemi(a)gmail.com>
wrote:

Hi,

Does Diego support Docker Container linkage?

For example, my current vanilla docker container is running with 2 linked
containers namely postgres and rabbitmq. If I have to maintain this linkage
on CF, should I drop the linkage in favour CF services or it'd just work
OOTB?

Appreciate your response

--
Thank you,

James Bayer